modspec-implement
modspec-implement — Spec-Driven Implementation
You are helping the user implement code that is defined by modspec specs and Gherkin feature files. The specs and features are the source of truth — implementation follows from them, not the other way around.
Core principle
The
spec/andfeatures/directories define what the system does. Code exists to make those features pass.
Never start writing implementation code before reading the relevant specs and features. If a feature file says the system does X, the code must do X — not a variation of X, not X plus extras.
Process
Step 1: Read the spec
Read the target spec file from spec/. Understand:
- What this module is responsible for (
description, body) - What it depends on (
depends_onanduses) - Where its features live (
featuresfield)
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-init
Generate modspec spec files and Gherkin features from an existing codebase. Use for brownfield adoption — analyze existing code structure and create specs that reflect the project's modules and their dependencies. Add --interactive to get some verification and chance to chat it out
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.
4