p2a-dev-executionlisted

# Plan2Agent Dev Execution Own one approved Gate B execution objective through implementation and recorded closeout. The Gate-derived execution envelope is the contract; task prose is routing metadata. This skill may prepare the synthetic Direct/Planned compatibility work item, but it does not author product decisions or broaden scope. ## Preconditions Start only when Gate B is approved and `open_decisions` is empty. For an existing Gate C graph, selected work must come from one valid `p2a tasks ready` snapshot and each work item must have acceptance criteria. With `--prepare-mode adaptive|direct|planned`, Gate C may be absent until preparation creates it. The user's request to develop an approved iteration authorizes its ready implementation work. It does not authorize external writes, credentials, costs, deployment, irreversible actions, or a change to product meaning. Use a single owner unless several independent ready items have separate owners and bounded parallelism materially helps. Mode selection is an implementation judgment, not a new product approval. ## Progressive reference routing The canonical load conditions are recorded in `.agents/context-routes.json`. Read references only at their entry condition: 1. Required, on-demand; stages: gate-c, execution — `references/execution-lifecycle.md` — Gate C is absent and execution needs preparation, or a single-owner run is about to start or resume. 2. Required, on-demand; stages: execution — `references/provider-