← ClaudeAtlas

p2a-reviewlisted

Use when reviewing a Plan2Agent spec, implementation plan, or task graph for missing decisions and execution risk.
silbaram/plan2agent · ★ 0 · Code & Development · score 60
Install: claude install-skill silbaram/plan2agent
# Plan2Agent Review Review planning artifacts before implementation starts. ## Inputs - `spec_json`. - `task_graph_json`. - Optional intake artifact for decision traceability. - Optional `iteration.json` planning Memory state and cited Memory search reports. ## Output Return `review_json` (schema `p2a.review.v1`). An optional `review_report` Markdown view may be generated from the JSON for human review. `review_json.blocking_issues` must be an empty array when the review passes with no blockers. `review_json` includes `schema_version`, `projectId`, `sourceSpec`, `sourceTaskGraph`, and: - `blocking_issues` - `non_blocking_risks` - `missing_tests_or_acceptance_criteria` - `oversized_tasks` - `dependency_issues` - `schema_or_gate_issues` - `evidence_or_citation_issues` - `recommended_changes` ## Required Checks - `spec_json.approval` is `approved` before task graph readiness is claimed. - `spec_json.open_decisions` is empty. - Approved Gate B status includes `spec_json.approval_audit` with `approved_by`, `approved_at`, `approved_artifacts`, and `approval_note`. - Every intake `CQ-n` appears exactly once in `spec_json.clarifying_question_disposition`. - No raw `CQ-n` id appears in `spec_json.open_decisions`; unresolved blockers from clarifying questions must be promoted to `ND-n`. - Every promoted clarifying question decision is either listed in `open_decisions` while unresolved or has a `resolution` before approval. - Every task dependency references an existing task id