phoenix-ambiguity-hunterRole 05 of the Phoenix Security spec pipeline. Red-teams normative requirements for Phoenix-specific failure modes: multi-tenant isolation gaps, vague integration surface definitions, AI agent safety holes (PSC-08), missing auth controls (PSC-06), reachability vs CVSS conflicts, RFC 2119 drift, comp
phoenix-batch-plannerRole 09 of the Phoenix Security spec pipeline. Slices a Phoenix Security feature into safe, incremental batches sized for a 12-person team (1–3 engineer-days each), with P0 security requirements always in Batch 1, API contracts before consumers, integrations last, explicit rollback strategies for ir
phoenix-constraint-distillerRole 03 of the Phoenix Security spec pipeline. Distils SCOPE_DEFINITION into an ACTIVE_SET of 8–15 compact, testable constraints that govern all downstream requirements — drawing from Phoenix's 12 Standing Constraints (PSC-01 through PSC-12) covering AWS/GCP infra split, 12-person team capacity, mul
phoenix-context-curatorRole 01 of the Phoenix Security spec pipeline. Cleans raw input — notes, tickets, Slack threads, customer call transcripts — into a structured CLEAN_CONTEXT block of FACTS, DECISIONS, and OPEN_QUESTIONS, tagged with Phoenix domain vocabulary, customer account labels (Mimecast, Johnson Matthey, Anapl
phoenix-contract-architectRole 07 of the Phoenix Security spec pipeline. Turns Phoenix Security requirements into precise implementable contracts: REST API endpoints with Phoenix auth patterns, tenant isolation invariants, cursor-based pagination (for 100K+ vuln record volumes), standard response envelopes, event schemas wit
phoenix-final-gateRole 10 of the Phoenix Security spec pipeline. Makes the final SHIP / NO_SHIP decision for a Phoenix Security feature spec by checking 8 hard blockers: critical ambiguities remaining, unverified MUSTs, multi-tenant isolation gaps (PSC-03), auth layer coverage (PSC-06), AI agent safety violations (PS
phoenix-orchestratorRun the full Phoenix Security spec pipeline (roles 01–10) from raw context to a ship-ready PRD — automatically chaining context curation, scope cutting, constraint distillation, requirements engineering, ambiguity hunting, security threat modelling, contract design, verification mapping, batch plann
phoenix-pipeline-navigatorInteractive guide and launcher for the Phoenix Security spec pipeline. Asks where you are in the process, what you want to do next, and routes you to the right skill with the correct inputs. Use this skill whenever someone says "where do I start", "what should I do next", "help me with the pipeline"
phoenix-requirements-engineerRole 04 of the Phoenix Security spec pipeline. Converts Phoenix Security feature intent into testable RFC 2119 requirements with structured IDs (R-FUNC, R-SEC, R-REL, R-INT, R-PERF, R-UX, R-DX, R-COMP), P0/P1/P2 priorities, and full traceability to active constraints. Covers functional, integration
phoenix-scope-cutterRole 02 of the Phoenix Security spec pipeline. Converts CLEAN_CONTEXT into an explicit, minimal SCOPE_DEFINITION — goals, non-goals, in/out boundaries, assumptions, success metrics, and gating questions — anchored to Phoenix's product pillars and 12-person team constraints. Use this skill when you h
phoenix-security-engineerRole 06 of the Phoenix Security spec pipeline. Produces a threat model and security requirements grounded in Phoenix Security's actual architecture: 6 trust boundaries (tenant↔platform, platform↔integrations, platform↔AI/LLM, platform↔CI/CD, platform↔AWS, CTI↔GCP), high-value asset inventory (vuln d
phoenix-verification-matrixRole 08 of the Phoenix Security spec pipeline. Maps every MUST/MUST NOT to a concrete proof method using Phoenix's proof type hierarchy: unit-test, integration-test, contract-test, static-analysis, infra-check, load-test, manual-review. Enforces that security requirements use static-analysis + unit-
prd-generatorGenerate a full security-focused PRD (Product Requirements Document) from a plain-language feature description. Use this skill whenever someone wants to create a PRD, product spec, feature spec, requirements document, or says things like "write a PRD for", "create a spec for", "plan this feature", "