Skip to content

DRY-RUN.md

Latest commit

 

History

History
63 lines (46 loc) · 1.71 KB

DRY-RUN.md

File metadata and controls

63 lines (46 loc) · 1.71 KB
Raw

Dry Run

This example shows the shape of a FactoryOS run without requiring application code.

The dry run is intentionally documentation-first. It should create or update planning artifacts before any product implementation begins.

Input

/factory "Add media catalog search with WCAG metadata"

Expected Behavior

  1. Create feature slug: media-catalog-search.
  2. Create or update .specs/media-catalog-search/spec.md.
  3. Create or update .specs/media-catalog-search/plan.md.
  4. Create or update .specs/media-catalog-search/tasks.md.
  5. Create or update .specs/media-catalog-search/validation.md.
  6. Create or update .tasks/YYYY-MM-DD-media-catalog-search-TASKS.md.
  7. Pick the first unblocked P0 task.
  8. Execute only that bounded task.
  9. Run QA if code changed.
  10. Record verification and progress.
  11. Stop at the approval gate.

Expected Output

Factory Run

Intent:
Add media catalog search with WCAG metadata.

Feature:
media-catalog-search

Created/Updated:
- .specs/media-catalog-search/spec.md
- .specs/media-catalog-search/plan.md
- .specs/media-catalog-search/tasks.md
- .specs/media-catalog-search/validation.md
- .tasks/YYYY-MM-DD-media-catalog-search-TASKS.md

Executed:
MCAT-001 - Map current ownership and data sources.

Verification:
No product code changed. Mapping complete.

Next:
MCAT-002 - Implement the first approved bounded slice.

Approval Gate:
Human review required before implementation.

Notes

  • The exact task IDs should match the generated task tracker.
  • The command should not claim tests passed unless tests ran.
  • If the adopted project has no runnable package commands yet, record that clearly.
  • Stop at the approval gate before creating implementation code.