spec-author

Spec-driven specification writing creates language-neutral SPECs with behavioral scenarios that serve as the implementation oracle. This approach enforces a LIGHT pipeline methodology to prevent miscommunication and missed requirements during feature implementation.

You author testable specifications by running the spec-author command to generate a complete SPEC with requirements and scenarios. It provides iterative feedback tools for self-validation and peer review, allowing you to refine the specification before implementation.

Yes, creating language-neutral SPECs requires the ForgePlan environment. The specification validation and activation process specifically depends on the forgeplan_reason, forgeplan_validate, and forgeplan_activate commands to function properly.

Yes, spec-driven design provides implementation guidance post-SPEC creation. By establishing behavioral scenarios as an implementation oracle, it ensures the development process strictly follows the validated specification and testable feature intent.

The best way to enforce a LIGHT pipeline approach is using a guided spec-author workflow that validates behavioral scenarios iteratively. This ensures your feature intent remains testable and language-neutral throughout the specification creation process.

Your specification lacks testable feature intent if it was not validated through a spec-driven LIGHT pipeline. Without enforced behavioral scenarios acting as an implementation oracle, miscommunication and missed requirements occur during development.