Agent Skills
› pony-maggie/code_minions
› plan-tasks
plan-tasks
GitHub将结构化产品需求文档分解为最多8个原子实施任务,明确验收标准和文件路径,按依赖顺序输出,确保每个任务可在单次专注运行中完成。
Trigger Scenarios
需要拆解PRD为可执行任务时
生成实现批次列表时
Install
npx skills add pony-maggie/code_minions --skill plan-tasks -g -y
SKILL.md
Frontmatter
{
"llm": {
"max_tokens": 12000,
"temperature": 0.2,
"max_iterations": 5
},
"name": "plan-tasks",
"inputs": {
"structured_prd": {
"type": "object",
"required": true
}
},
"outputs": {
"tasks": {
"type": "array"
}
},
"policies": {
"cache": true,
"max_tasks": 8
},
"description": "Decompose structured PRD into atomic implementation tickets.",
"allowed-tools": [],
"required-mcps": []
}
plan-tasks
Turn a structured PRD into a small list of implementation batches.
Inputs
structured_prd(object, required): output of parse-prd.
Instructions
- Return at most 8 tasks. For a small or medium PRD, target 3-6 tasks.
- Each task should be an implementation batch that groups related small requirements, not a micro-ticket.
- Each task must be small enough to implement in one focused run.
- Each task must include explicit acceptance criteria (Gherkin-style preferred).
- Each task must include
expected_paths: a conservative list of file globs the task is expected to own, such as["src/**", "tests/**"]. Keep it narrow enough to catch unrelated edits, but broad enough for normal implementation and tests. - For bootstrap tasks that create a Web/Vite app, include scaffold and config
paths such as
package.json,index.html,vite.config.*, andtsconfig*.jsonalong withsrc/**and test paths. - Respect dependencies: output tickets in implementation order.
- Do NOT invent features not present in
structured_prd. - Preserve negative constraints and rule exceptions exactly. Do not turn a forbidden behavior into a positive acceptance criterion.
- For grid movement apps, if the PRD forbids 180-degree reverse turns,
every keyboard and mobile-control task criterion must respect that rule:
up <-> downandleft <-> rightare illegal immediate reversals. Test legal mobile turns from a non-opposite current direction instead of expecting an immediate opposite turn to succeed. - Do not write
delivery_profileyourself. The runtime injects the authoritativestructured_prd.delivery_profileinto every task after planning. - The runtime injects
trace_idfor tasks that omit it. If you provide atrace_id, keep it stable and unique within this plan.
Reply with a single JSON object.
Outputs
tasks(object[]):{id, trace_id?: string, title, description, acceptance_criteria: string[], expected_paths: string[], depends_on: string[], delivery_profile?: object}
Version History
- ac75593 Current 2026-07-24 17:41


