name: project-mgmt description: > Spec-driven development with persistent markdown planning. Use when: complex tasks (>5 tool calls), multi-step work, GitHub issues, research tasks, building projects. Creates plan.md, spec.md, findings.md, progress.md in .project/{issue#}/ directory.

Project Management

Spec-driven development with filesystem as persistent memory.

Core Principle

Context window is volatile. Filesystem is persistent. Anything important gets written to disk.

Workflow Phases

Each phase has its own reference file. Read the appropriate one:

Phase	When	Reference
Start	Initialize project	`references/start.md`
Specify	Define requirements	`references/specify.md`
Plan	Create approach	`references/plan.md`
Implement	Execute steps	`references/implement.md`
PR	Create pull request	`references/pr.md`
Sync	Update GitHub	`references/sync.md`

Files

File	Purpose
spec.md	Requirements (what & why)
plan.md	Implementation steps + session context
findings.md	Research, decisions
progress.md	Session log, errors

Location: .project/{issue#}/ Templates: assets/

Key Rules

•Create plan.md before starting work
•Save findings after every 2 search/view operations
•Log all errors to progress.md
•Re-read plan.md before major decisions
•Run the pm-bookkeeper agent in the background for file updates