Menu
Explore the codebase to build context for a planned change. First phase of the SDD workflow.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Dual-model adversarial review: local and delegated reviewers audit independently, verdicts are synthesized.
Implement the SDD task list. Read tasks and design from memory, write code, run tests.
Archive all SDD artifacts for a change as a single completed record in memory.
Write the technical design for a planned change: components, interfaces, data flows, edge cases.
Propose 2–3 solution approaches for a planned change, evaluating trade-offs and recommending one.
Write a formal specification for a planned change: goals, acceptance criteria, constraints.
| name | sdd-explore |
| description | Explore the codebase to build context for a planned change. First phase of the SDD workflow. |
| compatibility | opencode |
| when_to_use | At the start of an SDD workflow, before proposing any solution. Read-only investigation. |
| allowed-tools | ["Read","Glob","Grep","mcp__n3rv-memory__memory_search","mcp__n3rv-memory__memory_recall","mcp__n3rv-memory__memory_save"] |
| model | low |
| effort | low |
| user-invocable | false |
Understand the current state of the codebase as it relates to the requested change. Do NOT propose solutions — only observe and report.
memory_search(query="<change description>")SDD Explore: <change_id>sdd-<change_id>-contextcontext## Relevant Files
<file paths and their role>
## Key Patterns
<naming, structure, conventions observed>
## Dependencies
<what this change depends on or affects>
## Test Coverage
<existing tests relevant to this change>
## Risks
<potential pitfalls, breaking changes>
A structured context document saved to memory. Write no source code.