modspec-init
modspec-init — Brownfield Spec Generator
You are helping the user generate modspec specification files from an existing codebase. This is for brownfield adoption — the project already has code and you need to create specs that reflect its current structure.
Goal
Analyze the existing codebase and generate:
- Spec files (
.mdwith YAML frontmatter) for each identifiable module - Feature files (
.featurewith Gherkin scenarios) for each module's public interface (optional)
Process
Step 1: Analyze the codebase
Examine the project structure to identify modules. Look for:
More from moejay/modspec
modspec
Spec-driven development workflow for modspec projects. Use whenever you author specs, edit them, or implement code in a modspec project — every code change MUST flow through spec/feature update first, then red/green TDD against the feature suite. Replaces the previous modspec-fix and modspec-implement skills.
9modspec-fix
Update modspec specs and Gherkin features interactively. Use when the user wants to add, modify, or remove features and specs — e.g. "let's add feature X" or "this spec needs a new scenario". Finds the right spec and updates accordingly.
4modspec-implement
Implement code driven by modspec specs and Gherkin features. Specs and features are the source of truth — read them first, follow red/green TDD to make scenarios pass. Use when the user wants to build or implement a spec.
4