Menu
Internal methodology for architect-owned test architecture. Produces structured testing strategy prose inside the architecture discovery marker.
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 | test-architecture |
| description | Internal methodology for architect-owned test architecture. Produces structured testing strategy prose inside the architecture discovery marker. |
| version | 1.0.0 |
| category | methodology |
| internal | true |
| triggers | test architecture, test strategy, coverage risks |
| metadata | {"gobby":{"audience":"agent","depth":0}} |
Use this skill when acting as the architect discovery-stage agent.
Capture the testing strategy needed to guide downstream planning, expansion, implementation, and QA. Focus on risks, coverage boundaries, and infrastructure needs. Do not create task sections.
Write only this section shape:
## Test Architecture
### Integration
- **<plan-section or surface>**: <what to verify>
### E2E
- **<plan-section or workflow>**: <full-flow scenario>
### Regression
- **<plan-section or bug class>**: <bug class to defend against>
### Contract
- **<surface>**: <surfaces that must agree>
### Infrastructure
- **<infra need>**: <new fixture, helper module, harness>
If unit tests are enough, write:
## Test Architecture
Unit tests sufficient - no additional test types recommended.
Do NOT write ### N.N task sections or PRD acceptance criteria.