v0.8.1

v0.8.1

This release refines FastSpec’s Loop Runner workflow and adds Codex plugin metadata.

Changes

• Added role-based Loop Runner artifact templates for planning, implementation, verification, review, and reporting.
• Updated Loop Runner and workflow docs for clearer state tracking and validation evidence.
• Added .plugin/plugin.json for plugin discovery.
• Removed generated example specs from the repository.

v0.8.0

Highlights

LoopSpec v0.8.0 introduces the new Loop Runner workflow for stateful, verifiable implementation after PRODUCT and TECH gates are approved.

What's Changed

• Rebranded the workflow around LoopSpec.
• Added spec-loop-runner as the post-gate implementation skill.
• Added spec-workflow as the top-level LoopSpec orchestration skill.
• Added Loop Runner artifacts:
  • LOOP_STATE.json
  • VERIFY.md
  • REPORT.md
• Added docs/loop-runner.md with runner profiles, result classifications, stop conditions, and escalation rules.
• Extended scripts/lint-specs.mjs with:
  • --spec <id-or-path>
  • --require-loop-artifacts
  • structural validation for loop artifacts.
• Clarified agent-specific skill install guidance.

Migration Notes

• Use spec-workflow instead of the old spec-driven-workflow entry point.
• Use spec-loop-runner instead of the old spec-implement entry point.
• GATES.json remains unchanged and still only stores PRODUCT and TECH approval state.

Validation

• node scripts/lint-specs.mjs
• node scripts/lint-specs.mjs --spec specs/08-feature-loop-runner-implement --require-loop-artifacts

v0.7.0

Summary

v0.7.0 is a documentation and workflow clarity release for Spec-Driven Development. It adds standalone reference docs for the staged workflow, skills, gate state, and Figma-backed UI flow, while tightening validation guidance for implementation.

Highlights

• Added docs/workflow.md to explain why the PRODUCT -> TECH -> IMPLEMENT workflow exists and how it runs.
• Added docs/skills.md to document the role of each skill and how the skills coordinate.
• Added docs/gates-json.md to explain the minimal GATES.json model, valid states, transitions, and linting.
• Added docs/figma-workflow.md to describe how Figma context feeds PRODUCT, TECH, and IMPLEMENT phases.
• Streamlined the README with a clearer overview image and documentation links.
• Tightened implementation guidance so validation evidence maps back to PRODUCT behavior IDs and important BDD-style examples.

Changed

• Clarified that implementation requires both PRODUCT and TECH gates to be approved.
• Expanded validation expectations for tests, manual checks, screenshots, visual artifacts, and fallback evidence.
• Improved workflow documentation for keeping specs current when implementation changes behavior or technical approach.

v0.6.0

What's Changed

This release extends the spec-driven workflow with optional BDD-style examples for behavior specs.

Added

• Added guidance for optional B*-E* examples under PRODUCT.md behavior invariants.
• Added a new example spec set at specs/bdd-style-behavior-examples.
• Added lightweight spec linting with scripts/lint-specs.mjs.

Updated

• Updated README positioning from product-first to behavior-first SDD.
• Updated spec-write-product, spec-write-tech, spec-driven-workflow, and spec-implement guidance so examples clarify behavior without replacing numbered invariants.
• Updated the behavior reference example to show concrete Given / When / Then-style scenarios.

Validation

• node scripts/lint-specs.mjs
• git diff --check

v0.5.0

What's Changed

• Added Figma-backed design contract support for spec-driven UI work.
• Added the fifth core skill:
  • spec-use-figma-design
• Updated the existing workflow skills with visual contract, implementation mapping, and visual verification guidance:
  • spec-driven-workflow
  • spec-write-product
  • spec-write-tech
  • spec-implement

v0.4.1

What's Changed

• Expanded the project README with installation, usage, architecture, and project structure documentation.
• Documents the four core skills:
  • spec-driven-workflow
  • spec-write-product
  • spec-write-tech
  • spec-implement