team-council-planlisted
Install: claude install-skill TokiDEV/team-skills
# team-council-plan
The second half of the council workflow. `team-council` decides **what**; `team-council-plan` produces the **how** — a reviewed implementation plan grounded in that decision.
## Preconditions
- **A resolved decision**: read the most recent (or user-specified) file in `.council/decisions/YYYY-MM-DD-<topic>.md`. If none exists, the council hasn't run — stop and point the user to `team-council` first.
- **Project profile**: read `.council/project-profile.md` (run `team-scan` if missing).
## Flow
```
Load decision + profile
↓
Draft plan (uses writing-plans conventions if available)
↓
Role review (parallel): CTO (technical soundness, sequencing, risk)
PO (scope, value, priority ordering)
+ any specialist the decision implicates
↓
Reconcile review feedback → revised plan
↓
Present plan to CEO for approval
↓
Write plan to docs/plans/YYYY-MM-DD-<topic>.md (or project's plan location)
```
### 1. Load context
Read the decision file and the profile. Extract the accepted direction, the trade-offs the council explicitly accepted, and any dissenting views worth guarding against.
### 2. Draft the plan
Produce a step-by-step implementation plan. If `superpowers:writing-plans` (or the project's planning skill) is available, follow its conventions. The plan must honor the council's decision — it implements the chosen direction, it does not relitigate it.
### 3. Role review (para