Generate product artifacts (roadmaps, PRDs, vision docs, changelogs, status reports) from beads state, brainstorms, and project context. Routes to artifact-specific phases after shared discovery.
From interpathnpx claudepluginhub mistakeknot/interagency-marketplace --plugin interpathThis skill uses the workspace's default tool permissions.
SKILL-compact.mdphases/changelog.mdphases/cuj.mdphases/discover-monorepo.mdphases/discover.mdphases/prd.mdphases/propagate.mdphases/roadmap-monorepo.mdphases/roadmap.mdphases/status.mdphases/vision.mdreferences/output-templates.mdreferences/source-catalog.mdFetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Retrieves current documentation, API references, and code examples for libraries, frameworks, SDKs, CLIs, and services via Context7 CLI. Ideal for API syntax, configs, migrations, and setup queries.
Uses ctx7 CLI to fetch current library docs, manage AI coding skills (install/search/generate), and configure Context7 MCP for AI editors.
You are generating a product artifact. Follow these steps exactly.
The user wants one of: roadmap, prd, vision, changelog, status, cuj, monorepo-roadmap, propagate
If not clear from the invocation, ask which artifact to generate.
If the user requests a roadmap and the CWD appears to be a monorepo root, automatically use the monorepo-roadmap path instead. A directory is a monorepo root if it has both:
.beads/ database (or beads CLI available with data).claude-plugin/plugin.json or CLAUDE.md filesAND it does not itself have a .claude-plugin/plugin.json at its root.
If the CWD is a monorepo root and the user requested "roadmap", treat it as "monorepo-roadmap".
Based on the artifact type:
artifact-gen/phases/discover.md and execute the discovery phase.artifact-gen/phases/discover-monorepo.md and execute the monorepo discovery phase.Based on the artifact type, read and follow the corresponding phase file:
| Type | Phase File |
|---|---|
| roadmap | artifact-gen/phases/roadmap.md |
| prd | artifact-gen/phases/prd.md |
| vision | artifact-gen/phases/vision.md |
| changelog | artifact-gen/phases/changelog.md |
| status | artifact-gen/phases/status.md |
| cuj | artifact-gen/phases/cuj.md |
| monorepo-roadmap | artifact-gen/phases/roadmap-monorepo.md (template-then-fill) |
| propagate | artifact-gen/phases/roadmap-monorepo.md → artifact-gen/phases/propagate.md |
For propagate: first generate the monorepo roadmap, then run the propagation phase to push items to sub-module roadmaps.
Write the generated artifact to the appropriate location (typically docs/ in the project root). If the file already exists, show a diff summary before overwriting.
After writing a roadmap or monorepo-roadmap artifact, run a bead consistency check:
iv-* IDs from the generated roadmap markdownbd show <id> should return successbd list --status=open and cross-referenceIf there are zero errors, print a one-line confirmation: "Roadmap-bead consistency: all IDs verified."
If the standalone audit script exists at scripts/audit-roadmap-beads.sh, you may call it instead of performing the checks manually. Both approaches produce equivalent results.
Skip this step for non-roadmap artifacts (prd, vision, changelog, status).