From wicked-garden
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 claudepluginhub mikeparcewski/wicked-garden --plugin wicked-gardenThis skill uses the workspace's default tool permissions.
Convert existing monolithic requirements documents into the graph structure.
Provides Ktor server patterns for routing DSL, plugins (auth, CORS, serialization), Koin DI, WebSockets, services, and testApplication testing.
Conducts multi-source web research with firecrawl and exa MCPs: searches, scrapes pages, synthesizes cited reports. For deep dives, competitive analysis, tech evaluations, or due diligence.
Provides demand forecasting, safety stock optimization, replenishment planning, and promotional lift estimation for multi-location retailers managing 300-800 SKUs.
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.md