prd-writerlisted

# PRD Writer Write the requirements portion of the shared execution contract. Keep user intent and observable behavior clear; implementation decisions belong in the plan on the same issue. A bounded task needs a compact issue, not an inflated PRD. ## Contract Inputs: - Request, target repository/issue, available product context, and constraints. - Draft versus publication mode and existing authorization. Outputs: - Requirements draft with current behavior, complete desired outcome, scope, EARS acceptance criteria, delivery coverage, dependencies, and verification needs. Creates/Modifies: - Requested canonical requirements document or authorized issue body. - No implementation and no automatic decomposition. External Side Effects: - Read-only research; authorized requirements publication only. Confirmation Required: - Ask only for a missing destination, consequential intent, or write authority that cannot be resolved from the session. Existing same-scope authorization carries through. An orchestrator's draft mode produces a draft without writes. Delegates To: - `prd-quality-gate` for the canonical template and draft lint. - `writing-plans` when invoked to plan settled requirements. - Recommend `feature-intake` for complete preparation from a rough request. ## Workflow 1. Resolve the canonical destination from session/repository context. Prefer the existing tracker issue; use one local document only when that is the requested workflow. Search issues