042 — tp idea add captures an idea at code level 3; tp roadmap add is refused there (#239)
Status: in progress Roadmap: #232
Why
Agent flow begins with capture
(agent flow): a
thought is stored as an issue labelled idea before anyone asks
whether it is good, in seconds, and only an interview moves it on, to
the roadmap, to a story or to closed. tp has one way to store a
thought, tp roadmap add, which puts it straight on the roadmap in an
epic. At level 3 that is the path the manual closes: nothing reaches
the roadmap except through an interview.
What changes
tp idea add TEXT...(new): at code level 3, files an issue titled TEXT and labelledideaon the release remote's forge, creating the label when the repository lacks it.ROADMAP.mdis not touched.tp roadmap addat code level 3 is refused, namingtp idea add.checkandarchiveare unchanged.docs/idea.md(new);docs/roadmap.mdsays whereaddstops.
Acceptance
maturity.code |
Command | Outcome |
|---|---|---|
| 3 | tp idea add TEXT... |
an issue titled TEXT, labelled idea; prints #N url; ROADMAP.md unchanged |
| 3 | tp idea add TEXT..., no idea label on the forge |
the label is created, then as above |
| 3 | tp idea add with no text |
error: an idea needs its text; no issue |
| 3 | tp idea add, the issue made but not labelled |
error naming the issue and the label |
| 0, 1 | tp idea add TEXT... |
error: ideas are captured at code level 3; names tp roadmap add; no issue |
| 3 | tp roadmap add TITLE... |
error naming tp idea add; no issue, ROADMAP.md unchanged |
| 0, 1 | tp roadmap add TITLE... |
as today |
| any | tp idea with another subcommand, or none |
usage |
Out of scope
- Moving an idea on: to the roadmap, to a story, or closed (#233). Until then a level 3 project has no command that adds a roadmap item.
- Listing ideas:
tp issue listshows the label. - A body for the idea. Capture is one line; the interview writes the rest.
Decisions
None. tp idea add is refused below level 3 because the manual shows a
project none of agent flow until it declares the level.
Done when
- tests express the acceptance table and pass
- spec updated
- ADR written if a fork was resolved
- roadmap ticked and stamped; changelog entry
- issue closed with a link to the release