Skip to content

feat: dogfood content allocation pattern on autonomous-dev's own files (Stream A) #1120

@akaszubski

Description

@akaszubski

Summary

Apply the content allocation pattern (proven in realign) to autonomous-dev's own CLAUDE.md, PROJECT.md, and memory directory. Dogfood the pattern before extending the plugin to ship it for other repos.

Implementation Approach

  1. Refactor CLAUDE.md (144 → ≤100 lines): remove Session Analytics SQL block (duplicates global CLAUDE.md), move long Commands list to docs/COMMANDS.md if not already there, keep rules + paths + pointers + canonical link to CONTENT_ALLOCATION.md.
  2. Refactor .claude/PROJECT.md (366 → ≤150 lines): consolidate purpose/architecture/scope; move operational content (periodic maintenance tables, batch sequences) to docs/RUNBOOK.md.
  3. Sweep autonomous-dev memory dir (18 files → ~12) using concrete criteria:
    • <500 bytes AND not active finding → delete (stub)
    • >3KB AND reads-like-doc → move to docs/
    • Content is just "[rule] — see CLAUDE.md" → delete
    • session_*_outcomes.md >7 days old → delete
    • RESOLVED/DONE/SUPERSEDED markers → delete
  4. Write docs/development/CONTENT_ALLOCATION.md in autonomous-dev's repo (manually authored, mirrors realign's). This becomes the canonical template in Issue Command Discoverability Broken: 21 advertised, only 8 exist #3.
  5. Update MEMORY.md index entries to reflect deletes/moves; keep entries ≤150 chars.

Acceptance Criteria

  • CLAUDE.md ≤100 lines
  • .claude/PROJECT.md ≤150 lines
  • MEMORY.md ≤200 lines (fits load window)
  • docs/development/CONTENT_ALLOCATION.md exists and matches realign's pattern
  • Memory file count reduced; no rule duplicates of new CLAUDE.md remain
  • All existing autonomous-dev tests pass (pytest --tb=short -q)
  • git diff review: no behaviour changes, only content reorganisation

Notes

This is Stream A of the broader retrofit plan (see .claude/plans/content-allocation-retrofit.md). Stream B (plugin extension) is Issues #2-#4 and depends on this work landing first.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions