Skip to content

AGENTS.md

Latest commit

 

History

History
43 lines (28 loc) · 2.3 KB

AGENTS.md

File metadata and controls

43 lines (28 loc) · 2.3 KB
Raw

SDD Pilot — Agent Context

Apply the Spec-Driven Development rules below during feature delivery. Enforce the lifecycle order, phase gates, conventions, and execution policy. If any rule here conflicts with project-instructions.md, follow project-instructions.md.

Lifecycle

Specify → Clarify → Plan → Checklist (optional) → Tasks → Analyze (optional) → Implement → QC

Treat this order as strict. If a required artifact for the next phase is missing, stop and return the work to the phase that owns it.

Phase Gates

  • spec.md must exist before Clarify or Plan.
  • plan.md must exist before Tasks.
  • tasks.md must exist before Implement.
  • If checklists/ exists, all checklist items must be complete before Implement unless the user explicitly overrides.
  • .completed must exist before QC.
  • Do not treat a feature as release-ready until .qc-passed exists.
  • Any project-instructions.md violation is CRITICAL severity.

Core Conventions

  • Store Feature Workspace artifacts in specs/<feature-folder>/.
  • New Feature Workspaces use 00001-feature-name folder names.
  • If the active branch matches #####-feature-name, use specs/<branch-name>/.
  • Existing non-prefixed Feature Workspaces remain valid when already present.
  • P1 is the most critical priority and should be sufficient for a viable MVP. Each user story or objective must be independently testable.

Markers:

  • .completed means implementation is complete.
  • qc-report.md records QC results.
  • .qc-passed means QC has passed.

Artifact preservation, format grammars (task / requirement / success-criterion / checklist / bug-task / stress-test-finding), and section rules live in .github/skills/artifact-conventions/SKILL.md. Do not duplicate them here.

Communication Style

Follow project-instructions.md section IV (Agent Output Style). That section is authoritative; do not duplicate or paraphrase its rules elsewhere.

Continuous Execution Policy

Execute routine repository operations for real: file edits, build/test/lint commands, git commands, task updates, marker files, and local package installs. Do not simulate completion, test results, QC results, or pass states. Stop only for ambiguity, destructive actions, system-level installs, or actions outside the project boundary. Report progress at phase boundaries.