메뉴
Synthesize the current conversation into a PRD and publish to the issue tracker. No interview — use what you already know.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Delivery overlay — orchestrates lean ladder, tdd, prune, review with sub-phase gates; commits only on user approval.
Flow Conductor for the aiops bundle. One entry — infers task type, shows plain-language steps, tracks journey in flow.state.yaml, dispatches skill + agent per phase.
Structured design process for the architect agent. Guides from grill conclusions to complete NOTES.md + tech-spec.md plus needed domain documentation updates through constraint gathering, module identification, interface design, alternative exploration, and risk analysis. Use when the architect needs to produce design decisions and technical specifications.
Build and query a persistent code graph for the target project. Uses graphify (Tree-sitter + Louvain clustering) for deterministic structural extraction, then the model adds semantic annotations. Use when the user says build graph, code graph, dependency graph, impact analysis, or when other skills need structured code understanding before proceeding.
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick. Use when the user says architecture review, codebase health, deepening, refactor suggestions, or complains about architectural friction.
Review in three modes — code (diff vs standards/spec), design (NOTES + tech-spec before planning), drift (implementation vs tech-spec before ship). Pick mode from Flow Conductor phase or user intent; do not mix artifact types.
| name | to-prd |
| description | Synthesize the current conversation into a PRD and publish to the issue tracker. No interview — use what you already know. |
| disable-model-invocation | true |
Synthesize context into a PRD. Do not interview — use the conversation and codebase.
Run /aiops-setup if docs/agents/issue-tracker.md or triage labels are missing.
CONTEXT.md vocabulary and local ADRs.ready-for-agent label.Problem Statement — user-facing problem.
Solution — user-facing solution.
User Stories — numbered As a <actor>, I want <feature>, so that <benefit> (extensive list).
Implementation Decisions — modules, interfaces, architecture, schema, API (no file paths; prototype snippets OK if they encode a decision).
Testing Decisions — what good tests look like, modules to test, prior art.
Out of Scope
Further Notes
When the PRD describes changes to an existing system (not a greenfield feature), use delta format instead of the full template above. Focus only on what changes:
# PRD: <slug> (delta)
## Context
One paragraph on what already exists and why it's changing.
## Changes
### ADDED
- New behavior or interface being introduced
- New modules, endpoints, or data structures
### MODIFIED
- [existing behavior] → [new behavior]
- [existing interface] → [updated interface]
### REMOVED
- Deprecated behavior being removed
- Modules or interfaces being deleted
## Impact
- Which existing modules are affected
- Migration path for breaking changes
## Testing
- What existing tests need updating
- New tests for added/modified behavior
## Out of Scope
When to use delta: if tech-spec.md references modifications to existing modules (not purely new code), prefer delta format. The conductor or planner should suggest delta when the architecture scan or design reveals significant existing code involvement.