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

phoenix-constraint-distiller

Role 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, multi-tenant isolation, integration surface, AI agent safety posture, and compliance hooks. Use this skill when you have a scope definition and need to produce the constraint set that locks down requirements, or when someone says "what are the constraints for this feature", "distil the active constraints", "what must always be true here", or "constraint layer for this spec". Always run after phoenix-scope-cutter and before phoenix-requirements-engineer.

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

安装与使用

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

npx skills add Security-Phoenix-demo/security-skills-claude-code --skill phoenix-constraint-distiller

技能说明


name: phoenix-constraint-distiller description: > Role 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, multi-tenant isolation, integration surface, AI agent safety posture, and compliance hooks. Use this skill when you have a scope definition and need to produce the constraint set that locks down requirements, or when someone says "what are the constraints for this feature", "distil the active constraints", "what must always be true here", or "constraint layer for this spec". Always run after phoenix-scope-cutter and before phoenix-requirements-engineer.

Phoenix Security — Constraint Distiller (Role 03)

Token Budget: ≤700 tokens Depends On: Role 02 — SCOPE_DEFINITION Feeds Into: Role 04 — Requirements Engineer Output: 03-active-set.md


Phoenix Standing Constraints (PSC)

Evaluate all for inclusion. Include only those relevant to the current feature.

IDConstraintTypeProof Hint
PSC-01AWS = onboarding + core; GCP = Phoenix CTI + AI/LLMoperationalconfig/IaC
PSC-02Team = 12 people; no feature assumes >2 dedicated engineersoperationalplanning
PSC-03Multi-tenant: customer data MUST be isolated at storage + query layersecuritytest + static
PSC-04API ingestion MUST support: GitHub AS, Snyk, Qualys, Wiz minimumfunctionalcontract test
PSC-05Vuln prioritisation MUST incorporate reachability, not CVSS-onlyfunctionaltest
PSC-06All new endpoints MUST authenticate via Phoenix auth layersecuritystatic + test
PSC-07No direct competitor brand names in user-facing copycompliancemanual review
PSC-08AI agents: assistive-only, disabled by default, no autonomous data ingestionsecuritytest + manual
PSC-09Customer data ingestion requires explicit opt-insecurity/compliancecontract + manual
PSC-10Phoenix brand: ≤2 accent colors per visual; RFC 2119 in all specsux/docmanual
PSC-11Container lineage: image build → registry → deployment MUST be preservedfunctionaltest
PSC-12Regulatory hooks: US (NIST) and UK (NCSC, Cyber Essentials) documentedcompliancemanual

Core Rules

  1. Constraints must be actionable and testable.
  2. No duplicates — merge overlapping constraints.
  3. No "nice-to-have" fluff.
  4. Do not invent constraints; if suspected but unconfirmed → CONSTRAINT_OPEN_QUESTIONS.
  5. Always include ≥1 security constraint (PSC-03 or PSC-06 or equivalent).
  6. Always include ≥1 operational constraint reflecting team size (PSC-02 or equivalent).
  7. If PSC-03 not included and feature touches customer data → flag as blocker.

Output Schema

---
meta:
  role: 03-constraint-distiller
  session_id: session-[YYYYMMDD-HHMMSS]
  token_count: [actual]
  status: complete | blocked
  next_role: 04-requirements-engineer
---

### ACTIVE_SET

#### ACTIVE_CONSTRAINTS (8–15)
- AC1: <constraint>
  (type: functional|reliability|ux|security|compliance|operational)
  (proof_hint: test|contract|static|manual)
  (source: PSC-NN | G?/IS?/D?)

#### CONSTRAINT_OPEN_QUESTIONS (max 7; blockers only)
- CQ1: ...

Chaining

Save: outputs/{session-id}/03-active-set.md → Pass to: phoenix-requirements-engineer (Role 04)