| name | architect-propose |
| description | Propose and create a new Architect track for an initialized project, including its spec, plan, metadata, and registry entry. Use when the user asks to add, plan, or propose a new feature, bug fix, chore, refactor, docs, or test track. |
Architect Propose
Create one proposal track from approved specification and plan artifacts. Follow references/propose-track-protocol.md as the source of truth.
Hard Boundaries
- Require initialized core Architect context.
- Do not create a track before both spec and plan approvals.
- Keep writes and links under safe
architect/ paths.
- Do not let unrelated track status block an independent proposal; only collisions may block creation.
- Commit only when explicitly requested in the current conversation.
Run
- Read
references/propose-track-protocol.md and core project context.
- Establish description and inferred track type.
- Draft, present, revise, and approve
spec.md.
- Draft, present, revise, and approve
plan.md from the project workflow.
- Recover management paths when needed, generate a safe ID, and run collision checks.
- Create artifacts, register the track, and report next steps without starting implementation.