# Autodev State

## Current Step
flow: greenfield
step: 6
name: Decompose
status: in_progress
sub_step:
  phase: 3
  name: decompose-step2-task-decomposition
  detail: |
    Step 1 (Bootstrap) and Step 1.5 (Module Layout) approved by user. Step 2 task PLAN approved
    (97 implementation tasks across 18 epics — see chat plan table). Two new epics created during
    Step 2 prep: AZ-264 (E-CC-HELPERS) re-homes the 8 shared helpers per the cross-cutting rule;
    AZ-265 (E-DEMO-REPLAY) adds offline replay mode (video + tlog → JSONL per-tick coordinate
    stream; subprocess-shaped UI integration; no ROS dependency). epics.md and module-layout.md
    updated to reflect both new epics. Per user's choice (option D), Step 2 EXECUTION
    (~290 MCP calls to write specs + create tickets + rename files) is deferred to a fresh chat.
    Resume in fresh chat by reading this state file + epics.md + module-layout.md, then
    iterate epic-by-epic in dependency order: AZ-245, AZ-246, AZ-247, AZ-264, AZ-248, AZ-249,
    AZ-250, AZ-251, AZ-252, AZ-253, AZ-254, AZ-255, AZ-256, AZ-257, AZ-258, AZ-259, AZ-260,
    AZ-261, AZ-265 (replay tasks last; depend on every C1–C5 epic).
retry_count: 0
cycle: 1
tracker: jira

## Resume notes (fresh chat handoff)

When resuming Step 2 execution in a fresh chat, the agent should:

1. Read `_docs/_autodev_state.md` (this file).
2. Read `_docs/02_document/epics.md` (canonical E-* ↔ AZ-NN map; rows 17–21).
3. Read `_docs/02_document/module-layout.md` (file-ownership map for the implement skill).
4. Read `_docs/02_tasks/todo/AZ-263_initial_structure.md` (already-completed bootstrap task spec).
5. Replay any leftovers in `_docs/_process_leftovers/` per `tracker.mdc`.
6. Begin Step 2 execution one epic at a time, in the order listed above. Per-epic
   per-task workflow: write `todo/[##]_[short_name].md` → create Jira ticket parented to
   the right epic → rename file to `todo/[AZ-NN]_[short_name].md` → update Tracker/Epic
   fields inside the file → repeat. Brief progress note after each epic completes.
7. After all 19 epics' tasks are written, run Step 4 (Cross-Verification) to produce
   `_docs/02_tasks/_dependencies_table.md` and resolve any cross-task dependency drift.
8. Then auto-chain to Step 3 (Blackbox Test Tasks) for E-BBT (AZ-262) per the
   user's earlier choice to defer test-spec Phase 4 to the Decompose pass.