homeradar-retro-fit-spec

To add missing CAP-IDs to feature specifications, the skill looks up two-letter feature codes in the SDLC registry and assigns sequential CAP-IDs starting at 01 in document order, then updates the spec status and commits the changes to git.

The CAP-ID retro-fit process for HomeRadar specs involves inserting required [XX-CAP-NN] identifiers into capability bullets that lack them, changing the spec status to In Progress, and creating an isolated git commit for the modifications.

Yes, you need a git repository to retro-fit CAP-IDs in spec files because the skill stages the updated specification and generates a dedicated, isolated git commit containing only the retro-fit changes.

The best way to track unnumbered capabilities before retro-fitting is complete is to use the interim filename#capabilities reference format until the sequential CAP-IDs are successfully assigned and committed.

The SDLC registry file works with capability numbering by providing the lookup table for two-letter feature abbreviation codes, which are then combined with sequential numbers to generate the required [XX-CAP-NN] identifiers in the spec document.

No, updating the spec status field to In Progress is bundled into the retro-fit workflow, which stages all modifications and creates an isolated git commit containing the status update alongside the new CAP-IDs.