SKILL.md
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.
Process
- Explore repo if needed. Use
CONTEXT.mdvocabulary and local ADRs. - Sketch test seams — prefer existing, highest seam, fewest seams. Confirm with user.
- Write PRD (template below) and publish to issue tracker with
ready-for-agentlabel.
PRD template
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
Delta mode (brownfield changes)
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 ScopeWhen 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.