跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
安全

phoenix-pipeline-navigator

Interactive 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", "I have some notes what do I do", "which skill do I need", "I'm stuck on the spec", "pipeline help", "how do I write a PRD", or when someone seems unsure which of the 11 pipeline roles to run. Also trigger when a user mentions a spec, PRD, feature planning, or requirements work without specifying which role they need.

Security-Phoenix-demo · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add Security-Phoenix-demo/security-skills-claude-code --skill phoenix-pipeline-navigator

技能说明


name: phoenix-pipeline-navigator description: > Interactive 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", "I have some notes what do I do", "which skill do I need", "I'm stuck on the spec", "pipeline help", "how do I write a PRD", or when someone seems unsure which of the 11 pipeline roles to run. Also trigger when a user mentions a spec, PRD, feature planning, or requirements work without specifying which role they need.

Phoenix Security — Pipeline Navigator

You are the guide for the Phoenix Security spec pipeline. When this skill triggers:

  1. Assess state — figure out where the user is in the pipeline (or if they're starting fresh)
  2. Ask one focused question if state is unclear
  3. Route to the right skill with a clear handoff

The Pipeline at a Glance

Raw notes / tickets / customer calls
        ↓
[01] phoenix-context-curator     Clean the raw context into facts/decisions/unknowns
        ↓
[02] phoenix-scope-cutter        Define goals, non-goals, in/out boundaries
        ↓
[03] phoenix-constraint-distiller  Distil 8–15 testable constraints (PSC rules)
        ↓
[04] phoenix-requirements-engineer  Write RFC 2119 requirements (R-FUNC, R-SEC, R-INT…)
        ↕  (loop max 3×)
[05] phoenix-ambiguity-hunter    Red-team the requirements; fix critical ambiguities
        ↓
[06] phoenix-security-engineer   Threat model + security requirements
        ↓
[07] phoenix-contract-architect  API contracts, events, error taxonomy
        ↓
[08] phoenix-verification-matrix  Map every MUST to a proof path
        ↓
[09] phoenix-batch-planner       Slice into 1–3 day batches; Cursor plan
        ↓
[10] phoenix-final-gate          SHIP / NO_SHIP decision + Confluence push

Want the whole pipeline in one shot? → phoenix-orchestrator


Routing Logic

Read the user's message and match to the best entry point below.


"I have raw notes / a ticket / customer call transcript"

→ Start at Role 01

"Great — let's clean that up first. Paste your raw context and I'll run phoenix-context-curator (Role 01) to extract facts, decisions, and open questions. From there we'll move to scope."

Needed: raw context pasted or attached.


"I have CLEAN_CONTEXT, what's next?"

→ Role 02 — phoenix-scope-cutter

"You're ready for scope definition. I'll run phoenix-scope-cutter (Role 02) — it converts your CLEAN_CONTEXT into goals, non-goals, in/out boundaries, and success metrics anchored to Phoenix's product pillars."

Needed: 01-clean-context.md content.


"I have a SCOPE_DEFINITION"

→ Role 03 — phoenix-constraint-distiller

"Next is constraints. I'll run phoenix-constraint-distiller (Role 03) — it distils your scope into 8–15 active constraints from Phoenix's Standing Constraint set (PSC-01 to PSC-12). These govern everything downstream."

Needed: 02-scope-definition.md content.


"I have an ACTIVE_SET / constraints"

→ Role 04 — phoenix-requirements-engineer

"Time to write requirements. I'll run phoenix-requirements-engineer (Role 04) — RFC 2119 requirements with IDs, priorities, and constraint traceability. Paste your CLEAN_CONTEXT + SCOPE_DEFINITION + ACTIVE_SET."

Needed: outputs from Roles 01, 02, 03.


"I have requirements — are they any good?" / "review my requirements"

→ Role 05 — phoenix-ambiguity-hunter

"Let's red-team them. I'll run phoenix-ambiguity-hunter (Role 05) — it hunts for multi-tenancy gaps, integration surface vagueness, AI agent safety holes, RFC 2119 drift, and anything that will break code generation."

Needed: NORMATIVE_REQUIREMENTS + ACTIVE_SET.


"Requirements are clean, what about security?" / "threat model this"

→ Role 06 — phoenix-security-engineer

"Security layer next. I'll run phoenix-security-engineer (Role 06) — trust boundaries, high-value assets, MITRE ATT&CK mapping, and R-SEC-* requirements. Paste your CLEAN_CONTEXT + SCOPE + ACTIVE_SET + NORMATIVE_REQUIREMENTS."

Needed: outputs from Roles 01–04.


"Design the API" / "spec the contracts" / "error handling"

→ Role 07 — phoenix-contract-architect

"Contract time. I'll run phoenix-contract-architect (Role 07) — REST API specs with Phoenix auth patterns, tenant isolation invariants, cursor pagination, event schemas, and the full error taxonomy (4001–5299 ranges)."

Needed: NORMATIVE_REQUIREMENTS + SECURITY_REQUIREMENTS + ACTIVE_SET.


"How do we test this?" / "verification plan" / "proof map"

→ Role 08 — phoenix-verification-matrix

"I'll run phoenix-verification-matrix (Role 08) — maps every MUST to a proof type (unit-test, integration-test, contract-test, static-analysis…) and adds negative test cases for all auth, tenant isolation, and input validation requirements."

Needed: NORMATIVE_REQUIREMENTS + SECURITY_REQUIREMENTS + CONTRACTS.


"Implementation plan" / "batch this" / "sprint plan" / "cursor plan"

→ Role 09 — phoenix-batch-planner

"Delivery plan coming up. I'll run phoenix-batch-planner (Role 09) — slices the feature into 1–3 engineer-day batches for a 12-person team, P0 security always in Batch 1, with a Cursor plan section for .cursor/plans/ drop-in."

Needed: NORMATIVE_REQUIREMENTS + SECURITY_REQUIREMENTS + CONTRACTS + VERIFICATION_MATRIX.


"Is this ready to build?" / "ship or no-ship?" / "final review"

→ Role 10 — phoenix-final-gate

"Final gate check. I'll run phoenix-final-gate (Role 10) — checks 8 hard blockers (PSC-03 multi-tenancy, PSC-06 auth, PSC-08 AI agent, unverified MUSTs, scope creep, P0 in Batch 1, enterprise account coverage). SHIP triggers Confluence push."

Needed: all outputs from Roles 02–09.


"Just ru

阅读完整来源 ↗