WORK-036
ID:WORK-036Status:done

Update CLAUDE.md files for plan CLI usage

Priority:highComplexity:simpleSource:SPEC-022

Criteria completion

Criteria completion: 6 of 7 (86%) checked; history from Mar 23 to Mar 230%25%50%75%100%Mar 23Mar 23
Branches 3
History 4
  1. e900a90
    Created (done)by bjornolofandersson
  2. f262d7b
    Content editedby Claude
  3. c3cc430
    • ☑ Root `CLAUDE.md` Plan section uses `refrakt plan` commands in its workflow instructions
    • ☑ `plan/CLAUDE.md` workflow section references CLI commands for status transitions and checkbox toggling
    • ☑ Examples show real command invocations (e.g., `refrakt plan update WORK-001 --status in-progress`)
    • ☑ Documents `refrakt plan next` for finding the next work item
    • ☑ Preserves existing guidance about reading specs, decisions, and dependencies before implementing
    • ☑ Only documents commands that are actually implemented at time of writing (no stubs)
    by Claude
  4. b2ed9c3
    Created (ready)by Claude
    Add WORK-036: update CLAUDE.md files for plan CLI usage

Summary

Once the plan CLI commands are fully implemented, update the root CLAUDE.md and plan/CLAUDE.md files so that Claude Code sessions know how and when to use refrakt plan commands instead of manually editing Markdoc files.

Currently the Plan section in root CLAUDE.md and the Workflow section in plan/CLAUDE.md instruct Claude to manually edit status attributes and checkboxes in .md files. These should be updated to use the CLI equivalents (refrakt plan update, refrakt plan next, refrakt plan status, etc.) once those commands are available.

Acceptance Criteria

  • Root CLAUDE.md Plan section uses refrakt plan commands in its workflow instructions
  • plan/CLAUDE.md workflow section references CLI commands for status transitions and checkbox toggling
  • Examples show real command invocations (e.g., refrakt plan update WORK-001 --status in-progress)
  • Documents refrakt plan next for finding the next work item
  • Documents refrakt plan status for viewing project state (not yet implemented — skipped per "no stubs" criterion)
  • Preserves existing guidance about reading specs, decisions, and dependencies before implementing
  • Only documents commands that are actually implemented at time of writing (no stubs)

Approach

Straightforward text editing of two files. Should be done after the core commands (update, next, status) are all implemented and tested — those are the ones referenced in the workflow.

Dependencies

  • WORK-030 (plan update — done)
  • WORK-031 (plan next)
  • WORK-029 (plan status)

References

  • SPEC-022 (Plan CLI)