Menu
Internal methodology for the architecture discovery stage. Produces a concise Architecture Brief for product and planning handoff.
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
Instructions for using gcode CLI for code search and retrieval. Loaded on demand when project has a code index.
Pre-transition checklist for closing or reviewing tasks. Covers fresh verification evidence, commits, and memory gates.
Use when processing CodeRabbit review comments, CodeRabbit CLI reports, or `$gobby coderabbit [findings]` requests.
Use when creating, editing, or validating Gobby skills, especially when a skill must change agent behavior or become discoverable through gobby-skills.
Use when coordinating a full gobby build run for an epic or task, especially when the user assigns the current session as coordinator, asks for a coordination epic, wants build agents/worktrees monitored, or wants gobby build bugs fixed so future runs work unattended.
Router contract for provider-aware Gobby help and installed skill dispatch.
| name | architecture |
| description | Internal methodology for the architecture discovery stage. Produces a concise Architecture Brief for product and planning handoff. |
| version | 1.0.0 |
| category | methodology |
| internal | true |
| triggers | architecture brief, technical design, interfaces |
| metadata | {"gobby":{"audience":"agent","depth":0}} |
Use this skill when acting as the architect discovery-stage agent.
Translate ideation and research into technical direction. Capture the drivers, decisions, components, interfaces, and trade-offs that planning must preserve.
Write only this section shape:
## Architecture Brief
### Drivers
- <technical driver>
### Decisions
- <decision and reason>
### Components
- <component or module responsibility>
### Interfaces
- <API, storage, MCP, CLI, or file contract>
### Trade-offs
- <trade-off>
### Open Questions
- <question or "None">
Do not write implementation tasks or PRD acceptance criteria. Keep the brief actionable for the planner.