skills/product/requirements-migrate/SKILL.md
Convert monolithic requirements documents into graph-structured requirements directories. Parses user stories and acceptance criteria from existing docs and creates atomic graph nodes. Use when: "migrate requirements", "convert to graph", "split requirements", "restructure requirements"
npx skillsauth add mikeparcewski/wicked-garden requirements-migrateInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Convert existing monolithic requirements documents into the graph structure.
Read the monolithic requirements file and extract:
Map extracted content to graph nodes:
US-NNN directoryAC-NNN-{slug}.md fileNFR-NNN-{slug}.md files_decisions/DEC-NNN-{slug}.mdFor each area:
mkdir -p requirements/{area}
Write requirements/{area}/meta.md
For each story in area:
mkdir -p requirements/{area}/{US-NNN}
Write requirements/{area}/{US-NNN}/meta.md
For each AC in story:
Write requirements/{area}/{US-NNN}/{AC-NNN}-{slug}.md
For each NFR in area:
Write requirements/{area}/{NFR-NNN}-{slug}.md
Write requirements/meta.md (root)
Write requirements/_scope.md
Write requirements/_risks.md
Write requirements/_questions.md
After migration:
Move the original monolith to requirements/_archived/ so it's
preserved but not the active source of truth.
_questions.md that ACs need to be defined_questions.mddevelopment
--- name: large-scale-migration description: How to execute a LARGE MECHANICAL change across any codebase with LEVERAGE instead of an agent-grind or hand-edits — a cross-cutting migration, refactor, rename, dialect/framework/DB port, library adoption, or bulk transform. The map→transform→gate pattern: a deterministic transform driven by a source-of-truth map, proven by a differential-equivalence gate. Use when the work is "migrate all X to Y", "rename Z everywhere", "port to a new DB/dialect/fra
testing
v11 LLM-based work-shape classifier. Replaces the regex archetype detector with the model's own reasoning. Reads the user's prompt, picks the right archetype(s) from the catalog, identifies signals (blast_radius, novelty, reversibility, etc.), and persists to SessionState so subsequent turns steer correctly. Use when: the prompt_submit hook emitted a `<wg classify-due />` directive, OR explicitly invoked at session start, OR when re-classifying after the user changes scope mid-session.
tools
v11 work-shape archetype runner. When a prompt has been routed to one of the 9 archetypes (triage, explore, specify, decide, ship, review, incident, build, migrate), this skill is the entry point. It picks the right per-archetype playbook from refs/ and executes the phase shape declared in `.claude-plugin/archetypes.json`. Use when: a `<wg archetype="X">` or `<wg archetypes>` system-reminder tag appears, an explicit "let's run the X archetype" request, or when one of the per-archetype slash commands resolves to this skill.
development
Show or set the session intent variable. Intent gates how loud the framework is — simple-edit (silent), feature/research (synthesis directive), rigor (full crew context). Auto-detected on turn 1; this skill overrides explicitly. Sticky for the session. Use when: "set intent", "intent override", "/wicked-garden:intent", "make the framework quiet", "force rigor", "what's my intent".