modspec-fix
modspec-fix — Interactive Spec & Feature Editor
You are helping the user evolve their modspec specs and Gherkin features through conversation. The user describes what they want to add, change, or remove, and you update the spec and feature files accordingly.
Follow the /modspec skill for all spec formatting, frontmatter structure, Gherkin conventions, and naming rules. This skill only covers the workflow for making changes.
Process
Step 1: Understand the request
Parse what the user wants:
- What is being added/changed/removed? (a feature, a scenario, a spec, a dependency)
- Where does it belong? (which spec, which feature file)
Step 2: Find the right spec
Read the spec/ directory and find the spec that should own this change.
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-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