Skip to content

CLAUDE.md

Latest commit

 

History

History
100 lines (79 loc) · 2.51 KB

CLAUDE.md

File metadata and controls

100 lines (79 loc) · 2.51 KB
Raw

Scaffold-first operating policy

You are working in a scaffold-orchestrated project.

Main rule

Scaffold is the source of truth. Use specialist subagents proactively for bounded tasks. Do not let the root thread become the workspace for detailed implementation.

Context budget policy

Keep the root conversation under 60% of total context budget. Root thread should contain only:

  • requirement summary
  • current stage
  • active decisions
  • artifact index
  • active gap queue
  • latest validator result
  • next dispatch plan

Do not keep in root:

  • large code dumps
  • long logs
  • raw test output
  • repeated subagent reasoning
  • full documents already stored in artifacts/state

When root becomes noisy, compact aggressively and preserve:

  • current stage
  • unresolved gaps
  • latest decisions
  • artifact pointers
  • re-entry instructions

Delegation policy

Use specialist subagents proactively when a task fits their description. Dispatch one primary owner per gap. Use a secondary owner only when required.

Validation policy

delivery-validator is read-only. It must not patch implementation. If validation fails:

  1. write/update gap queue
  2. assign primary owner
  3. dispatch remediation
  4. re-run validation

Resume policy

On resume:

  1. load project summary
  2. load scaffold state
  3. load active gap queue
  4. announce current stage and next action
  5. continue from last checkpoint, not from scratch

Subagent output contract

Every subagent returns only:

  • decisions
  • artifact
  • risks
  • next_steps
  • handoff
  • done_criteria

Context compaction triggers

Run /compact after:

  • product shaping
  • architecture freeze
  • first validation pass
  • each remediation round

Slash commands

Command Purpose
/scaffold Start a new scaffold run
/resume-scaffold Resume from saved state
/validate Run delivery validation
/fix-gap Route a gap to its owner and re-validate
/plan-product Shape requirements with product-designer
/decide-stack Choose stack with tech-strategist
/continue-stage Continue the active stage from checkpoint

State files

All persistent state lives in .claude/state/:

  • scaffold-state.json — mode, stage, active plan, open gaps, next action
  • project-summary.md — compact human-readable summary
  • artifact-index.json — pointers to all produced artifacts
  • gap-queue.json — open gaps with owner assignments
  • validator-status.json — latest validation result
  • stage-checkpoints/ — per-stage checkpoint snapshots