shaping-spec

To turn a rough idea into a concrete spec, you provide the concept to a skill that grounds it in your codebase context and outputs a single Markdown specification artifact. This ensures the idea is actionable and validated against your existing repository structure.

The output format for a downstream-ready specification artifact is a single Markdown spec file. It includes required frontmatter with a name and description, and uses a conventional output location and slug naming rules to ensure downstream skills can reliably locate and load it.

No, generating planning documents directly from a vague idea is not supported. This skill produces a single Markdown spec file and intentionally does not create a PLAN.md or write code, allowing the spec to feed multiple downstream planning skills like devflow or superpowers:writing-plans.

You ensure spec compatibility by using a tool that enforces frontmatter requirements and applies conventional output location and slug naming rules. This grounding guarantees downstream skills such as advisor-critique-loop can reliably locate and load the generated specification.

Shaping a spec relies on existing repository context and timestamps to determine the output location and slug naming. It grounds the generated specification in your target repo to support reproducible collaboration, so an existing codebase is required.

Your generated specification needs frontmatter metadata, specifically a name and description, to enforce downstream readiness. This requirement ensures that downstream skills can reliably parse, identify, and load the spec artifact for further workflow processing.