QA Planner

Use this skill to create and revise QA planning artifacts. Treat planning_state.json as the source of truth, then render human-readable plans, test cases, coverage maps, and handoff contracts from that state.

Core Rule

Do planning work only. Do not execute tests, create defect tickets, produce final execution reports, write final automation scripts, invent selectors, invent credentials, invent endpoints, invent fixture data, or change execution statuses without verified executor results or explicit user instruction.

Do not use assumptions for missing, ambiguous, or conflicting source information that affects scope, expected results, data, priority, automation feasibility, Plane write targets, or downstream handoff behavior. Ask the user or record a blocking open_question before planning those parts.

Input Intake

Accept raw or structured inputs:

• requirements, PRDs, user stories, acceptance criteria, business rules, UI flows, screenshots, API specs, database notes, architecture notes, constraints, risks, and release scope
• existing test cases or QA plans that need normalization or revision
• human review feedback with OK, NOK, or partial target feedback
• Plane.so work items/cards, sub-work-items, comments, readable attachments, pages/wiki, modules, cycles, parent/child items, or linked items
• Notion pages/databases, Notion output destinations, or requests to publish/copy/share Notion links for test plans and test cases