AI SDLC Kit
Reference

Artifacts Reference

Every artefact generated by the AI SDLC Kit β€” who creates it, who reads it, and when.

Discovery artefacts (Flow A)

ArtefactLocationCreated byRead byWhen
idea.mddoc-specs/idea.md🧭 Discovery (/discovery-refine)πŸ—‚οΈ PMAfter idea.txt is ready
non-technical-spec.mddoc-specs/non-technical-spec.mdπŸ—‚οΈ PM (/discovery-spec)πŸ§‘β€πŸ’Ό Tech LeadAfter idea.md approved
PRD.md (project)doc-specs/PRD.mdπŸ§‘β€πŸ’Ό Tech Lead (/discovery-prd)πŸ—οΈ ArchitectAfter functional spec approved
technical-spec.mddoc-specs/technical-spec.mdπŸ—οΈ Architect (/discovery-tech-spec)πŸ—οΈ Architect (epic init)After PRD approved
epics.mddoc-specs/epics.mdπŸ—οΈ Architect (/discovery-epics)πŸ—οΈ Architect (epic init)After technical spec approved
CONTEXT.md (initial)doc-specs/CONTEXT.mdπŸ—οΈ Architect (/discovery-tech-spec)All agentsCreated once, updated after each epic

Per-epic artefacts (Flow A)

Created in doc-specs/<N>-epic/ for each epic N.

ArtefactLocationCreated byRead byWhen
epic-N.mddoc-specs/<N>-epic/epic-N.mdπŸ—οΈ Architect (/epic-init)πŸ—οΈ Architect, humanStart of epic Spec phase
PRD.md (per-epic)doc-specs/<N>-epic/PRD.mdπŸ—οΈ Architect (/epic-init)πŸ› οΈ Implementer, πŸ”Ž ReviewerAfter epic-N.md approved
spec-epic-N.mddoc-specs/<N>-epic/spec-epic-N.mdπŸ—οΈ Architect (/epic-init)πŸ› οΈ Implementer, πŸ§ͺ QA, πŸ”Ž ReviewerGate before Epic phase
decisions-log.mddoc-specs/<N>-epic/decisions-log.mdπŸ—οΈ Architect (empty, via /epic-init)πŸ”Ž Reviewer, πŸ—οΈ Architect, πŸš€ OpsCreated empty; filled by πŸ› οΈ Implementer
ops-epic-N.mddoc-specs/<N>-epic/ops-epic-N.mdπŸš€ Ops (/epic-close)Human, πŸ—οΈ ArchitectAfter review approved; before deploy
incident-log.mddoc-specs/<N>-epic/incident-log.mdπŸš€ Ops (/ops-triage)πŸš€ OpsCreated on first incident; appended on each triage

Flow B artefacts

ArtefactLocationCreated byRead byWhen
tarefa.mddoc-specs/tarefa.mdπŸ“₯ Intake (/task-init)πŸ“ PlannerAfter tarefa.txt is ready
PRD.mddoc-specs/PRD.mdπŸ“ Planner (/task-prd)πŸ“ Planner, πŸ› οΈ ImplementerAfter tarefa.md approved
spec.mddoc-specs/spec.mdπŸ“ Planner (/task-spec)πŸ› οΈ Implementer, πŸ§ͺ QA, πŸ”Ž ReviewerGate before implementation

Project-level artefacts

ArtefactLocationCreated byRead byWhen
CONTEXT.mddoc-specs/CONTEXT.mdπŸ—οΈ ArchitectAll agents (before each epic)Created once; updated after each epic via /context-sync
AGENTS.mdProject rootπŸ“ Planner (/agents-init)GitHub Copilot (all interactions)Once per project

Artefact flow diagram

idea.txt
   ↓ /discovery-refine
idea.md
   ↓ /discovery-spec
non-technical-spec.md
   ↓ /discovery-prd
PRD.md
   ↓ /discovery-tech-spec
technical-spec.md + CONTEXT.md
   ↓ /discovery-epics
epics.md
   ↓ /epic-init <N>  (repeats per epic)
doc-specs/<N>-epic/
   β”œβ”€β”€ epic-N.md
   β”œβ”€β”€ PRD.md
   β”œβ”€β”€ spec-epic-N.md    ← implementation gate
   └── decisions-log.md
   ↓ /task-implement
   (code + filled checklist + decisions-log.md entries)
   ↓ /task-tests
   (test report)
   ↓ /task-review
   (review report)
   ↓ /epic-close <N>
doc-specs/<N>-epic/ops-epic-N.md
   ↓ /context-sync <N>
CONTEXT.md (updated)

Retention and versioning

All artefacts should be committed to version control. They serve as the audit trail for every decision made during the lifecycle of the project.

  • Never delete entries from decisions-log.md
  • CONTEXT.md is append-only for completed epics and ADR sections
  • Superseded specs should be versioned or kept alongside their epic folder, not deleted