arrow_back Back to Rules
rules Rule

Artifact Standard

Standardizes how the agent creates and manages technical artifacts — plans, walkthroughs, and tasks — ensuring every important decision is persisted to disk.

Artifact Standard — Artifact-Driven Development

This rule standardizes how the agent creates and manages technical artifacts. Every important decision must be persisted to disk — not just kept in ephemeral conversation context. This is the core of Artifact-Driven Development.

1. Implementation Plans

Location: Projects/[project-name]/artifacts/plans/plan-YYYY-MM-DD-description.md

Every plan MUST include:

  • Objective — detailed goal
  • Technical Plan — step-by-step breakdown
  • Verification Checklist — tests to confirm success
  • Rollback Strategy — how to revert if needed

2. Walkthroughs (Evidence)

Location: Projects/[project-name]/artifacts/walkthroughs/walkthrough-description.md

Every walkthrough MUST include:

  • Summary — what was implemented
  • Verification Log — results per checklist item
  • Evidence — terminal output, logs, screenshots

3. Task Management

Canonical store: Projects/[project-name]/artifacts/tasks/backlog.md.

  • MUST use checkboxes for tracking.
  • MUST define clear “Definition of Done” per task.
  • SHOULD use /backlog workflow for all task mutations.

4. Persistent Mirroring

MUST mirror internal thought artifacts (plans, tasks, walkthroughs) to the project artifacts/ directory. Internal agent state is ephemeral — mirroring ensures logic is persistent and human-auditable.

MUST update artifacts before or after major creative/architectural work.

Workflow

1. /plan create → artifacts/plans/
2. Implement   → reference plan, update checklist
3. /verify     → artifacts/walkthroughs/
4. /end        → sync task status

References

→ Back to Rules Catalog