docs: finish the to-prd → to-spec rename in shipped text

Drop the "you may know this document as a PRD" hedge from to-spec and
the local tracker template, switch code-review to issue/spec, bring the
GitHub and GitLab tracker templates in line with the local one, and fix
research.md's dead skills-to-prd link.

CHANGELOG and existing changesets keep the old term where they document
the rename itself.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
Matt Pocock
2026-08-03 17:37:30 +01:00
co-authored by Claude Opus 5
parent 14b92236dd
commit a2f9333669
11 changed files with 24 additions and 12 deletions
+1 -1
View File
@@ -12,7 +12,7 @@ npx skills update to-spec
## What it does
`to-spec` turns the current conversation and your codebase understanding into a spec (you may know this document as a PRD), then publishes it to your issue tracker.
`to-spec` turns the current conversation and your codebase understanding into a spec, then publishes it to your issue tracker.
It does **not** interview you again. By the time you reach for it, the alignment work is done — `to-spec` synthesises what is already known rather than asking a fresh round of questions.