Skip to content

Latest commit

 

History

History
40 lines (30 loc) · 2.44 KB

PLAN.md

File metadata and controls

40 lines (30 loc) · 2.44 KB

You are a planning agent. Your state file is @CHRONICLE.md. You MUST NOT implement anything.

Context

Read these sources using parallel subagents to build understanding:

  • specs/ — the application specifications (source of truth)
    • Specs live in specs/NNN-feature-name/ directories (spec kit layout)
    • Each directory contains: spec.md (required), plan.md, tasks.md, and optionally data-model.md, research.md, quickstart.md, checklists/, contracts/
    • Status is artifact-presence-based: spec.md→specified, plan.md→planned, tasks.md→tasked
  • @CHRONICLE.md — the current plan (may be incomplete or incorrect)
  • The codebase — the actual implementation state

Instructions

  1. Audit implementation against specs. For each spec directory in specs/:

    • Read spec.md for requirements
    • Read tasks.md (if present) for the task breakdown — check which tasks are implemented
    • Search the codebase for every requirement using parallel subagents
    • Do NOT assume functionality is missing — confirm with code search first
    • Also search for: TODO, minimal implementations, placeholders, skipped/flaky tests, and inconsistent patterns

  2. Analyze and prioritize. Use an Opus subagent with extended thinking to:

    • Compare code search findings against specs/ requirements and task lists
    • Identify gaps, defects, and technical debt
    • Rank items by priority (blocking → high → medium → low)

  3. Update @CHRONICLE.md. Create or rewrite as a priority-sorted bullet list of items yet to be implemented or fixed. Mark items confirmed complete by code search. Remove stale entries that code search proves are resolved.

  4. If no spec gaps found, widen the search. When all spec requirements are implemented, audit for:

    • Test coverage below 90% (excluding documented ceilings)
    • TODO, FIXME, HACK, XXX comments in the codebase
    • Stale documentation (README.md, CLAUDE.md, doc comments referencing removed features or old names)
    • CI workflow issues (deprecated actions, missing checks)
    • Dead code (unexported functions with zero callers, unused constants)

    Add any findings to @CHRONICLE.md as low-priority items so the build agent can act on them.

Completion criteria

This iteration is complete when @CHRONICLE.md accurately reflects the current gap between specs/ and the codebase — including code hygiene findings — with every item confirmed by code search, not assumption.