7ffbb1f757
- CLAUDE.md with collaboration rules and Planner/Generator/Evaluator cycle - .claude/ agents, commands, skills, hooks per Claude Code conventions - Sprint Contracts for sut-prober, normalizer, recorder, player, diff-reporter - SUT catalog (EG-BIM Modeler, 187 plugins) and .gitignore excluding SUT tree - PROGRESS.md / PLAN.md as shared agent handoff state - Solution scaffold targeting sut-prober PoC Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
768 B
768 B
name, description, allowed-tools
| name | description | allowed-tools |
|---|---|---|
| contract | Create or update a Sprint Contract for a module/feature via the planner agent. Usage /contract <module-name or short description> | Read, Write, Edit, Agent, Glob, Grep |
Create a Sprint Contract and PLAN.md entry for: $ARGUMENTS
Delegate to the planner subagent. The planner must:
- Read
PLAN.md,PROGRESS.md,CLAUDE.md, and relevant memory. - Write
docs/contracts/<slug>.mdwith the Sprint Contract template (Goal, DoD, Interfaces, Out of scope, Evaluation plan, Risks). - Add or update the corresponding
PLAN.mdentry with priority and dependencies. - Return a short briefing with file paths.
If $ARGUMENTS is empty, ask the user what to plan. Never write code into src/ — planning only.