decompose-requirementslisted

# Decompose Requirements ## Purpose Create or repair the Requirement Manifest for a lifecycle brief without hiding assumptions, renumbering existing IDs, or turning implementation details into requirements. This is a power skill, not a lifecycle phase. It supports Think and later repair/backfill work, but the Think phase owns the full brief artifact and approval checkpoint. ## Invocation Context Use this skill when: - a new Standard or Complex request needs a Requirement Manifest - an existing brief lacks `R`, `RI`, `A`, or `Q` structure - downstream artifacts need manifest IDs backfilled without renumbering - a user answer resolves or changes manifest questions - Review/Test/Ship finds missing requirement traceability Do not invoke it for Trivial work unless the user explicitly requests a manifest. ## What To Load **Foundation** (confirm in context; load if not already present): - Root `AGENTS.md` - `workflow/router.md` - `workflow/lifecycle.md` - `workflow/rules.md` **Minimum for invocation**: - This file - `references/output-schema.md` **Before starting work**: - `references/decision-tree.md` — to determine the mode (create, backfill, update, or no-op) - Existing brief artifact when backfilling or revising **Load when the step requires it**: - `references/explicit-requirements.md` — when extracting `R` IDs from user input - `references/implicit-requirements-library.md` — when deriving `RI` IDs from repo or config sources - `references/assumptions-and-questions.