prp-createlisted

Author a Product Requirements Prompt (PRP) for an Ignition multi-artifact feature. Use when the user asks to "plan", "scope", "structure", or "draft a blueprint" for work that touches more than one Ignition artifact (tags + SQL + views + scripts); use when the user says "before we start building, I want a structured plan"; use when the user names a feature that clearly spans multiple artifact types ("build the production-log dashboard", "replace the hand-written SCADA form with a proper Perspective view backed by a Named Query"); use when the user references PRPs directly ("write a PRP for X", "let's PRP this"). The skill produces a single markdown file at `<project-root>/prp/{slug}.md` following a strict section contract enforced by `scripts/validate_prp.py`. Execution of the PRP is a separate skill (`prp-execution`) — do not start emitting artifacts inside this skill. For single-artifact work (one tag, one query, one script), do NOT use this skill — invoke the domain skill directly. A PRP is overhead until
aimerfan/ignition-skills · ★ 0 · AI & Automation · score 60

Install: claude install-skill aimerfan/ignition-skills

# Ignition PRP Authoring ## What this skill does Converts a user's feature request into a Product Requirements Prompt — a structured, validation-ready planning document that captures scope, context, and a per-artifact blueprint. A PRP is not the implementation; it is the packet another Copilot session (or the same one, later) needs to build the feature correctly on the first pass. The Ignition adaptation of PRP comes from the CM framework's `prp-create.prompt.md` + `templates/prp.template.md`, collapsed from a multi-agent workflow into a single-Copilot human↔AI loop. What survives the adaptation is the **discipline** — scope challenge, evidence-first context, confidence gates, ambiguity escalation, progressive validation, anti-sycophancy. What doesn't survive is the researcher/architect/developer subagent orchestration (we don't use subagents in this framework yet). ## Critical preconditions — non-skippable Before authoring any PRP, confirm: 1. **Ground truth exists or is explicitly acknowledged missing.** Look for `<project-root>/ground-truth/`. If it's empty or absent, tell the user *before* proceeding: "I can draft a PRP without ground truth, but every artifact reference will be marked `[known unknown — verify in Designer]` and the PRP cannot reach HIGH confidence until real exports are added." Do not silently proceed as if the PRP were authoritative. 2. **The feature genuinely needs a PRP.** Apply the complexity test below. If it fails, redirect the user to the app