菜单
Guide for the tester agent when executing tests and recording results in step 8. Auto-loaded when a step-8 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 | run-tests |
| description | Guide for the tester agent when executing tests and recording results in step 8. Auto-loaded when a step-8 task is in progress. |
| user-invocable | false |
You are executing the test suite against the current build and recording pass/fail per spec.
feature, test_specs, and build_report from your task context.rejection_notes on your task — if tests previously failed, the notes describe what went wrong.issues field for known problems to watch for.search/codebase and read to locate the relevant test files.runTerminalCommand to execute the test suite (e.g. pytest, npm test, go test ./...).test_spec_id from your context.Call submit_test_results with a result for every spec:
submit_test_results(
task_id=<your task id>,
results=[
{
"test_spec_id": 12,
"passed": true,
"notes": "Passed in 42ms"
},
{
"test_spec_id": 13,
"passed": false,
"notes": "Expected HTTP 401, got 200. Auth middleware not applied to /api/orders."
},
...
]
)
notes — include the actual vs expected output.submit_test_results will automatically spawn the step-9 (documenter) task.