tp story
Development-method stories (see the method): one file per
story in docs/stories/NNN-slug.md, tracked by one issue on the release
remote's Forgejo.
| Command | Does | Prints |
|---|---|---|
tp story new TITLE... |
writes the next story from the template, status proposed |
the new file's path |
tp story issue NNN |
creates the story's issue and stamps (#N) onto its heading |
#N url |
Numbering — one above the highest NNN-*.md in docs/stories/,
starting at 001. The slug is the title's lower-case words joined by
hyphens, cut at a word boundary to 50 characters.
The issue is titled Story NNN: <title>. Its body is the first
paragraph of the story's Why section and a link to the file on the
current branch — push the story for the link to resolve. The file is the
source of truth; the issue is only ever written from it. issue refuses a
story that already has an issue or has no Why paragraph, and leaves the
file untouched if the forge call fails. Forge and token are resolved as
for tp issue.