Plan a feature or change
Turn a broader feature, specification or desired outcome into a reviewable dependency-aware plan without implementing code.
Use plan when a feature, specification, analysis item or desired outcome is too broad to implement safely as one bounded task.
Run planning
tcaf plan --target <project-path> --request "<feature or outcome>"
tcaf plan --target <project-path> --input <specification-or-analysis>TCAF reads the relevant current repository and project evidence before proposing the plan.
What you get
A useful plan makes visible:
- practical dependencies;
- work that is ready now;
- task boundaries;
- open decisions or blockers;
- the next executable unit of work.
A dependency is semantic: it describes something that must be true first, not merely an item that appears earlier in a list.
Review the plan
The developer reviews, changes, approves or rejects the proposal. Planning is preparation, not execution.
plan does not:
- implement application code;
- write Task Contracts;
- change project state;
- grant implementation approval.
Move one task into execution
When a proposed task is ready, create its separate authorization boundary:
tcaf task --target <project-path> --request "<approved bounded task>"The resulting Task Contract is reviewed independently before the AI can execute the approved work inside that boundary.