Skills

03 Shadow Areas

Scan a markdown artifact (idea, stories, PRD, spec) for blind spots into a shadow...

Install

npx skills add ai-driven-dev/framework --skill 03-shadow-areas -g -a claude-code -y
Category
Git and review
Updated
4d ago
License
MIT
Context cost
Lightabout 565 tokens
Runs scripts
No, instructions only

What it does

Scan a markdown artifact (idea, stories, PRD, spec) for blind spots into a shadow report grouped by category and severity. Use to find gaps or what is missing in a written artifact. Not for interactive Q&A or code review.

Shadow Areas

Analytically scans a written artifact for gaps the author has not addressed. Unlike iterative Q&A clarification, this skill reads the existing material and emits a structured report: each gap carries a category from a locked 7-category taxonomy, a 3-tier severity, and a direct-question probe the author can act on immediately.

Actions

#ActionRoleInput
01detectParse input, extract gaps, classify category and severity, emit probesfile path or inline text
02render-reportRender markdown grouped by category and sorted by severity, write reportgap list from detect
03diffLoad prior report, classify gaps as closed / still-open / newly-introducedgap list from detect + prior report path

Dispatch by context: with no prior report run detect then render-report; with one, run detect then diff. Before running an action, read its file in actions/, not only the table or assets.

Transversal rules

  • Never modify the source artifact.
  • Every gap carries all three: a category, a severity, and a probe question.
  • Every probe is a direct question ending with ?.
  • Categories and severities come from the locked sets in references/locked-sets.json.
  • When zero blockers and zero majors remain, stamp the report status: clean.
  • On re-runs, gaps are matched by category and snippet, never by question wording, so rephrasing a question never creates a spurious "newly introduced" gap.

References

Read the whole SKILL.md on GitHub

More in Git and review