prospec-taskslisted

<!-- Generated by `prospec agent sync`. Do not edit — this file is regenerated on every sync. --> # Prospec Tasks Skill ## Activation When triggered, briefly describe: - That you'll read plan.md and delta-spec.md to understand the implementation scope - Tasks will be organized by architecture layer following the project's conventions (see [`references/tasks-format.md`](references/tasks-format.md)) - Non-code tasks carry a `[M]`/`[V]` kind marker; complexity estimates and `[P]` markers are optional ## 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 standalone executable — the one-click installer script from the project README (macOS/Linux `install.sh`, Windows `install.ps1`) or a release binary from GitHub Releases; prospec is NOT published to npm. Then re-run this skill. 3. **Version older than 1.0.0** → STOP. Report the i