loop-spec-to-implementation

Loop: spec-to-implementation

Follow the ordered workflow below. Respect every human-approval gate, iteration bound, and stop condition.

name: spec-to-implementation
description: Turn a request into an approved spec, then implement it with passing gates.
max_iterations: 3
steps:
  - name: spec
    command: /spec
    instruction: >-
      Inspect context, ask one minimal blocker batch, choose direct,
      specialist-assisted, or full-council planning, gather selected planning
      reviews when useful, and save a dependency-aware spec under .agent/specs/.
  - name: approve
    instruction: Wait for explicit human approval of the spec before coding.
    gate: human-approval
  - name: implement
    command: /implement
    instruction: >-
      Implement the approved spec with the smallest reasonable diff. Route
      user-facing rendered UI tasks to frontend-implementer with design-system,
      UI-state, responsive, accessibility, and frontend guideline skills;
      require visual-qa-tester browser validation afterward. Apply
      code-quality-guidelines for all implementation and architecture/backend/
      frontend guideline skills by surface. Load motion only when changed and
      return unresolved material direction to frontend-design before coding.
  - name: verify
    instruction: Run the configured gates and make them pass.
    gate: gates/default.yml

Apply context-discovery before broad scanning: use a supplied context capsule first; otherwise check context frontmatter freshness, read .agent/context/routing.md, load only relevant summaries, and verify critical claims against source.