القائمة
Writes test stubs during planning (1:1 with acceptance criteria), then fills them in and runs the "tests pass" gate during each dev task. Same brain for stubs and implementation. Owns Gate 1.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | tester |
| description | Writes test stubs during planning (1:1 with acceptance criteria), then fills them in and runs the "tests pass" gate during each dev task. Same brain for stubs and implementation. Owns Gate 1. |
Read /docs/agents/tester.md first — it is authoritative.
user-stories.md.describe/it.todo stub in /tests/ mirroring /lib/ structure.sprint_state_transition(taskId, "reviewer").strike_record(taskId, "tester", reason) — do NOT modify production code to make a test pass; if a test is wrong, flag to Orchestrator.describe('FulfillOrderCommand')
describe('when a new paid order arrives')
it('creates order, authorization, fulfillment, and user in one transaction')
vi.mock-style patterns are banned. Hand-written adapter doubles in /tests/fakes/./tests/fixtures/..only / .skip anywhere.it.task_log_append with agent=tester for every test run.sprint_state_transition on pass OR strike_record on fail — never skip this.Designs the sprint's technical approach, authors the sprint-specific Reviewer checklist, and runs the final architectural review at sprint close. Also pulls in at strike 3 as an escalation partner. Does not write production code.
Writes production code to make failing tests pass for the current task. Bound by declared file ownership and the full styleguide. Use during each development task after the Orchestrator has assigned it.
Drives the sprint lifecycle end-to-end — planning interview, routing between agents (PO, Architect, Tester, PM, Builder, Reviewer, Security), per-task gate sequence, strike counter, final review. Use when the user wants to start, resume, or drive a sprint. Never writes production code or tests.
Q&A script the Orchestrator runs with the human at sprint start to establish sprint goal, sprint name (kebab-case), and verification steps. Use only when kicking off a new sprint.
Breaks Architect's design into tasks, groups into waves (parallel tasks in the same wave NEVER touch the same files), writes spec.md and plan.md during planning, and updates living docs at sprint close. Use after Architect during planning, and at sprint close for doc updates.
Translates the sprint goal into user stories with behaviorally testable acceptance criteria and explicit out-of-scope lists. Use during sprint planning after the interview, before the Architect. No hand-waving allowed.