メニュー
DEPRECATED — do not use. The monolithic design phase has been split into three phase-gated 1:1 skills. Use `proposal` (scope), then `spec` (behavior), then `design` (architecture), each behind its own grill/review gate.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use after the design phase is approved (proposal → spec → design complete). Translates the approved design into granular, ordered TDD task pairs — each behavioral task must have a failing test written before implementation. Each task must be completable in a single focused session.
Use when the agent starts a new turn or receives any request. This is the global methodology router — it MUST run before any other skill to determine the correct phase and enforce workflow discipline.
Parameterized Socratic challenge engine. Runs BEFORE drafting an artifact (proposal | spec | design | tasks), loading the matching references/grills/<phase>-grill.md and challenging one question at a time. Records agreed resolutions in the target artifact's Challenge & Resolution Log. Toggled by workflow level (strict = on).
Use when starting new work, a user provides a Jira key, or the enforcer routes to the initialization phase. Creates an SDLAIC change with full context from Jira and codebase research.
Parameterized auditor & gatekeeper engine. Runs AFTER an artifact is drafted (proposal | spec | design | tasks | code), loading the matching references/reviews/<phase>-audit.md in a clean subagent and issuing an APPROVE / REQUEST_CHANGES / REJECT verdict. Verdicts are persisted via `sdlaic gate set` — never inside the repo. For `code`, runs the two-pass compliance + quality review.
Use to author design.md for a change — the Technical Architecture phase (Phase 2). Runs after an approved spec and an optional design grill, producing the architecture that satisfies the proposal and spec, then hands off to the review gate.
| name | brainstorm |
| description | DEPRECATED — do not use. The monolithic design phase has been split into three phase-gated 1:1 skills. Use `proposal` (scope), then `spec` (behavior), then `design` (architecture), each behind its own grill/review gate. |
This skill is deprecated and must not be invoked.
brainstorm generated three artifacts — proposal.md, specs/, and design.md
— in a single pass. That bundling caused generative overreach: technical
design decisions were made on top of unverified business requirements, and no
runtime could enforce phase-by-phase boundaries. See
docs/.ideation/phase_gated_artifact_review_loops.md.
The design phase is now four independent, phase-gated micro-loops. Each has a dedicated 1:1 draft skill and its own grill-before / review-after gate:
| Instead of brainstorm's… | Use skill | Artifact | Gate checklists |
|---|---|---|---|
| Proposal step | proposal | proposal.md | grills/scope-grill.md, reviews/proposal-audit.md |
| Delta spec step | spec | specs/<capability>/spec.md | grills/spec-grill.md, reviews/spec-audit.md |
| Design step | design | design.md | grills/design-grill.md, reviews/design-audit.md |
Task decomposition remains in plan (gated by grills/plan-grill.md /
reviews/plan-audit.md).
The enforcer skill routes each phase through grill → draft → review → gate and
never routes to brainstorm. If you arrive here, stop and route to proposal
(or the correct current phase per sdlaic status + sdlaic gate status).
