메뉴
Guide for the tester agent when writing test specs in step 5. Auto-loaded when a step-5 task is in progress.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Create VS Code custom agents (.agent.md files) that define specialized AI personas with scoped tools, model preferences, handoffs, and hooks. Use when creating a new custom agent, configuring tool restrictions for a role, setting up agent handoffs for multi-step workflows, adding agent-scoped hooks, or deciding between agents vs prompt files vs skills.
Guide for the Project Initiation Manager when conducting the brief conversation. Covers all three entry paths (fresh start, rough brief, form JSON), the one-question-at-a-time conversation rules, completeness-driven question ordering, and how to generate the markdown brief.
Show pending tasks for a TaskFlow agent role. Lists what work is waiting and which project/feature each task belongs to. Use this to find out what an agent needs to do next.
Add TaskFlow to an existing project. Scans the workspace, detects existing agents/skills/MCP servers, and guides the user through creating a brief that captures what's already built.
Start a new TaskFlow project. Prompts for a project brief (file path or inline text), then hands off to the Project Initiation Manager to build and validate the brief before the Dev Manager configures the team. Use this to kick off a new development cycle.
Check for and apply pending TaskFlow schema migrations after pulling a new release.
| name | write-test-specs |
| description | Guide for the tester agent when writing test specs in step 5. Auto-loaded when a step-5 task is in progress. |
| user-invocable | false |
You are writing test specifications before any implementation begins. Your specs define what "passing" means for this feature.
feature and definitions_of_done from your task context.rejection_notes on your task if present — the previous submission was rejected.Each spec requires:
{token: string} in body")Optional but recommended:
description: "POST /users with valid payload creates user and returns 201"
expected_result: "HTTP 201, body contains {id: integer, email: string}"
rationale: "Covers DoD: user creation endpoint returns correct response"
strategy: "integration"
description: "POST /users with missing email returns 400"
expected_result: "HTTP 400, body contains {error: 'email is required'}"
rationale: "Covers DoD: invalid input is rejected with a clear error"
strategy: "integration"
expected_result: "no errors" ← not measurabledescription: "it works" ← not specificexpected_result: "200" ← missing body/content assertionsubmit_test_specs(
task_id=<your task id>,
specs=[
{
"description": "...",
"expected_result": "...",
"rationale": "...",
"strategy": "integration",
"order_index": 0
},
...
]
)