p2a-task-authorlisted

# Plan2Agent Task Author Author a reviewable Gate C task graph draft from an approved active Plan2Agent iteration context. This is a sibling to `p2a-task-breakdown`, but it writes only a draft and hands off to a human approval gate before any canonical task graph is promoted. ## Ownership - Draft authorship belongs to the read-only `p2a-task-author` subagent. - The skill owner obtains the context bundle, passes it to the subagent, reviews the returned draft JSON, and is the only agent that persists `task-graph.draft.json`. - If subagents are unavailable, the active skill owner may author the draft locally, but it must preserve the same authorship-versus-persistence boundary. ## When to use Use this skill when the active iteration has an approved Gate B spec and needs a Gate C task graph authored as a reviewable draft. The draft is agent-proposed work, not the canonical Gate C artifact; a human must review and approve it before promotion. ## Inputs The skill owner runs the context command to get the `p2a.task_context.v1` JSON bundle before invoking the task-author subagent: ```bash node .plan2agent/scripts/p2a_iteration.mjs context --artifacts <root> ``` Use these context fields: - `project_id` - `effective_spec.product` - `effective_spec.implementation` - `existing_tasks.active` - `existing_tasks.maintenance` - `spec_field_changes` - `planning_memory` - `idea` - `active_iteration` - `code_signals` Use `context.code_signals` (the real file tree and recent changed fi