prospec-backfill-speclisted

<!-- Generated by `prospec agent sync`. Do not edit — this file is regenerated on every sync. --> # Prospec Backfill Spec Skill ## Activation When triggered, briefly describe: - That you'll backfill a behavioral **Feature Spec draft** from existing **code** (not a design tool) for brownfield **features/capabilities** that have no Feature Spec coverage - That a feature is a **vertical slice** (one end-to-end capability across the modules that implement it) — not a module; one module can host several features and infrastructure modules host none - The draft records *behavior*, never *intent* — un-inferable intent is marked `[NEEDS CLARIFICATION]`, never fabricated - The draft is staged for human verify-and-promote and is **never** written to the trust zone (`prospec/specs/features/`) ## Language Policy Write each generated document in the language the Constitution's Language Policy rule assigns to **its path** — change artifacts and their archived summaries in the project's artifact language, the trust zone (Knowledge base, Feature Specs, index) in English. One skill run may write both. Keep code, identifiers, technical terms, and git commit messages in English. ## CLI Prerequisite (required) > The prospec CLI is a required file for this skill — its deterministic steps call `prospec` > commands. Probe BEFORE any other step; there is no manual fallback. 1. Run `prospec --version` (Bash). 2. **Command not found / not executable** → STOP. Ask the user to install the prospec