一键在 Manus 中运行任何 Skill

agent-task-compiler

星标0

分支0

更新时间2026年7月5日 09:49

Compiles a vague project idea into agent-ready work - a sprint spec, a contract of testable assertions, and an ordered task list with acceptance criteria. Use when the user wants to hand a project to Codex, Claude Code, or coding agents, break down a build, or turn an idea into tickets/tasks.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

Arnie016

Arnie016/fable-mythos

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

Agent Task Compiler

Mission

Turn "build me X" into artifacts an agent can execute for hours without drifting: spec → contract → tasks. The contract is what gets graded, not the vibe of the original ask.

Workflow

Preserve the boundary. Quote the user's original sentence verbatim at the top — it is the scope boundary everything else answers to.
Write the spec: what done looks like (one paragraph, outcome not activity) · in scope · out of scope · constraints (stack, must-not-break, reuse-not-rewrite). If the idea contains several products, force it to one and park the rest — ask one batched question only if genuinely blocked.
Negotiate the contract: 15–30 testable assertions. "Works well" is unfalsifiable; "searching 10k rows returns in under 2s" is a contract. Every assertion checkable by someone who didn't build it.
Compile the tasks: ordered, each sized to a single agent session (≤ half a day). Per task: goal, files likely touched, acceptance criteria referencing contract IDs (A01, A02…), and what the next task depends on from it.
Existing code changes everything. If a repo already exists, task 1 is always "audit current state and reconcile this plan against it" — never plan greenfield onto brownfield.
Flag the human decisions. Any task involving payments, auth design, data deletion, or external communications gets a NEEDS HUMAN marker with the specific decision required.

Boundaries

Decline to compile tasks for spam, mass-messaging, scraping that violates a platform's terms, or anything designed to deceive — offer the compliant version of the goal instead.

Output format

Original ask (verbatim)

Sprint spec

Contract

Numbered assertions A01–Axx.

Task list

Table: # · task · acceptance (contract IDs) · depends on · NEEDS HUMAN flags.

Parked

Anything cut from scope, in one line each, so nothing is silently lost.

同仓库更多 Skills

同仓库

skill-author

Arnie016/fable-mythos

Creates a new Claude Skill to fable-mythos standard - a tight SKILL.md plus eval cases and an example. Use when the user wants to turn a repeated workflow, a giant pasted prompt, or a recurring task into a reusable skill.

2026-07-050

video-prompt-director

Arnie016/fable-mythos

Turns a scene idea into production-ready prompts for AI video models (Seedance, Veo, Higgsfield, Kling, Sora). Use when the user wants video generation prompts, a scene broken into shots, camera directions, or is fighting inconsistent characters across generated shots.

2026-07-050

voice-capsule

Arnie016/fable-mythos

Builds a reusable personal style guide (voice capsule) from the user's real writing samples so any model can write closer to their voice. Use when the user wants output to sound like them, asks to capture their voice or style, or complains that AI writing sounds generic.

2026-07-050

linkedin-signal-posts

Arnie016/fable-mythos

Turns messy project notes into high-signal LinkedIn posts for AI, research, startup, hackathon, education, or technical audiences. Use when the user asks for a LinkedIn post, launch post, achievement post, founder update, research announcement, or polished social post.

2026-07-030

skill-repair-loop

Arnie016/fable-mythos

Repairs a Claude Skill after a bad output by identifying the exact failure, patching SKILL.md, and adding a regression test. Use when a skill output is generic, wrong, overhyped, off-format, or fails the user's expectations.

2026-07-030

name	agent-task-compiler
description	Compiles a vague project idea into agent-ready work - a sprint spec, a contract of testable assertions, and an ordered task list with acceptance criteria. Use when the user wants to hand a project to Codex, Claude Code, or coding agents, break down a build, or turn an idea into tickets/tasks.

Agent Task Compiler

Mission

Turn "build me X" into artifacts an agent can execute for hours without drifting: spec → contract → tasks. The contract is what gets graded, not the vibe of the original ask.

Workflow

Preserve the boundary. Quote the user's original sentence verbatim at the top — it is the scope boundary everything else answers to.
Write the spec: what done looks like (one paragraph, outcome not activity) · in scope · out of scope · constraints (stack, must-not-break, reuse-not-rewrite). If the idea contains several products, force it to one and park the rest — ask one batched question only if genuinely blocked.
Negotiate the contract: 15–30 testable assertions. "Works well" is unfalsifiable; "searching 10k rows returns in under 2s" is a contract. Every assertion checkable by someone who didn't build it.
Compile the tasks: ordered, each sized to a single agent session (≤ half a day). Per task: goal, files likely touched, acceptance criteria referencing contract IDs (A01, A02…), and what the next task depends on from it.
Existing code changes everything. If a repo already exists, task 1 is always "audit current state and reconcile this plan against it" — never plan greenfield onto brownfield.
Flag the human decisions. Any task involving payments, auth design, data deletion, or external communications gets a NEEDS HUMAN marker with the specific decision required.

Boundaries

Decline to compile tasks for spam, mass-messaging, scraping that violates a platform's terms, or anything designed to deceive — offer the compliant version of the goal instead.

Output format

Original ask (verbatim)

Sprint spec

Contract

Numbered assertions A01–Axx.

Task list

Table: # · task · acceptance (contract IDs) · depends on · NEEDS HUMAN flags.

Parked

Anything cut from scope, in one line each, so nothing is silently lost.