What problem does it solve? Deferred tasks in a documentation-driven development workflow often get lost or forgotten. This Skill provides a single source of truth (docs/devdocs/backlog.md) for parking, tracking, reactivating, and closing work items that are not yet ready for the current development cycle, without creating a new numbering system or duplicating Jira-style boards. ## Core Features & Use Cases - Park and Track Items: Register deferred items anchored to existing source IDs (F/US/AC/T/INS/BUG/FR/NFR/M) with a strict state machine (parked → reactivated / closed / superseded). - Reactivation Routing: Route reactivated entries to the correct downstream flow (requirements, dev-tasks, bugfix, insights, prd) with mandatory target_flow and target_id gating. - Schema Realignment: Migrate backlog.md structure across spec versions (backlog.v1 → v2) using a Migration Matrix with idempotent, structure-only fixes. - Use Case: During verification, a P3 edge-case issue is found but should not block the release. Park it via the backlog, then later reactivate it into dev-tasks as task T-08 when capacity allows. ## Quick Start Ask the AI to park a deferred item by running the backlog skill with a source ID, for example: park item F-01 into the backlog with a note explaining why it is deferred.