القائمة
Optional Analysis before PRD: route vague ideas through facilitated brainstorming and a concise product brief without creating tasks.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Bootstrap a Memory Bank for a new or existing repository, then route into PRD-driven or brownfield workflows.
Implementation handoff skill for one TASK-* using tier-selected protocol files, local gates, evidence, and explicit verification/sync handoff.
Turn a PRD into a traceable Memory Bank with product, requirements, epics, and features.
Clean up and maintain Memory Bank docs so they stay accurate and easy to load.
Set up deterministic commands, worktrees, and quality gates so agents can run safely in this repository.
Create the Memory Bank skeleton and project command proxies in the current repository.
| name | mb-analysis |
| description | Optional Analysis before PRD: route vague ideas through facilitated brainstorming and a concise product brief without creating tasks. |
/prd when the idea is vague, unstable, or needs explicit product framing./analysis when: you need a router that inspects current Memory Bank state and recommends the next command./brainstorm when: the idea is raw and needs facilitated ideation. The AI acts as a coach; the user's product intent and choices remain the source of truth./brief when: the concept is clear enough to produce a concise Product Brief, or after a brainstorming report exists..memory-bank/analysis/.Analysis is optional. Raw PRD text or an existing external PRD should pass /constitution first when project principles are not ratified/partial, then be normalized and checked through /write-prd, producing .memory-bank/prd.md with type: prd, clarification_status: complete, and constitution_checked: true; then /spec-init prepares the lightweight SDD route map before /prd decomposes it. After /prd, /spec-design is mandatory but adaptive: simple T0/T1 scope may record a minimal backbone, while shared/T2/T3 scope records the needed domain/model/contracts/state/security/runtime design. Brownfield projects should map the current codebase first with /map-codebase before planning deltas.
/brief creates the Product Brief as the input contract for /constitution and /write-prd. It is not a PRD, backlog, research report, or marketing document.
The normal planning path is:
/analysis -> /brief -> /constitution -> /write-prd -> /spec-init -> /prd -> /spec-design -> /spec-improve FT-<NNN> -> /prd-to-tasks FT-<NNN>
Use /brainstorm before /brief when the idea is raw. /constitution should read the Product Brief when present and run the governing-principles interview; if the user explicitly skips it, downstream PRD work may continue with framework-default/skipped principles.
Analysis never creates task records. /spec-design also does not create task records or feature-local implementation design; it only updates backbone SDD specs and spec-index, while /spec-improve FT-<NNN> remains the feature-level gate. /clarify-feature FT-<NNN> is optional and only for a specific feature that is explicitly pending/blocked or has decomposition-affecting unresolved markers.
.memory-bank/analysis/index.md.memory-bank/analysis/product-brief.md.memory-bank/analysis/brainstorming/BR-<NNN>.mdTemplates in assets/ are reference shapes for those artifacts. They are intentionally compact and can be adapted during interactive sessions.