What is not wired In flight
Issues, concerns and decisions are written specialty documents that nothing invokes. Saying so is cheaper than being found out.
The project-manager specialist declares six specialties. Three of them — issues, concerns and decisions — exist only as reference documents; no command reaches them. So the team's description promises issue-tracking, concern-flagging and decision-recording, and today it delivers scheduling.
Declared versus reachable
| Has a specialty document | Reachable by a command | |
|---|---|---|
| todos | yes | yes |
| schedule | yes | yes |
| dependencies | yes | yes |
| issues | yes | no |
| concerns | yes | no |
| decisions | yes | no |
And a stated dependency
The specialist's own sourcing section says project-management recipes and guidelines are still to be added to the cookbook, and that its specialties will reference them when they exist. That is the same shared-spine pattern every other team relies on, and it is the reason this team is the thinnest of the nine.
Why it ships anyway
Because a working schedule command is genuinely useful, and because a team that is honest about its own surface is a better neighbour than one that quietly no-ops. That is why this topic carries an in-flight marker rather than a shipped one: half the declared surface is real and the other half is named, not delivered.