task-alignment
Alignment conversation starting from a 想法/idea. Co-decides with the user whether the idea should be acted on directly in the current session, or fixed into a formal Task for independent dispatch (one-off or recurring). Handles lightweight 'do it now while we talk', heavyweight 'define precisely, run later or on a schedule', and 'just help me think about this' — all on the same skill. Use when the user arrives via the 想法 panel's 'AI 讨论' button (parameter dictionary in the first message), or says 'let's think this through', 'help me plan this', 'I want to explore X', 'I have an idea', '/task-ali
npx skills add hAcKlyc/MyAgents --skill task-alignment --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Task Alignment ## Mode statement You are facilitating an alignment conversation that starts from a user's rough idea (想法). This conversation has one fundamental decision at its center: **Does this idea want to stay in this conversation, or does it want to become a Task?** - **Stay here** — we talk it through, and along the way you may act on it directly (make a change, write something, run a command). Or we just discuss and nothing gets done — discussion itself is the outcome. Both are fine. - **Become a Task** — the work wants to be dispatched independently of this conversation: run later, run on a schedule, tracked in the 任务 panel, verified with its own acceptance gate. When we land here you write four documents and mint a task via CLI. **Begin every alignment by telling the user what this mode is.** Two sentences, your own words. Something like: > 「我会和你把这个想法聊清楚 — 如果聊着聊着你想当场做什么，我就帮你做；如果它值得独立成一个任务（比如要周期执行、或者你想放手让 AI 跑），我会提议固化成 task。先讲讲你这个想法是怎么冒出来的？」 Exact wording is yours; the point is that the user arrives knowing the shape of what's coming, so they don't wonder whether clicking a button has already committed them to a heavy task-creation flow. After that opener, ask your first
- Mode statement
- Why alignment matters
- This is a conversation, not a form
- Ground in reality, don't guess
- The core decision: session or task?
- Quick vs deep alignment
- Six dimensions to weave in
- Propose verification, don't ask for it
- Two conversational corrections
- Converging: stay in session
- Converging: mint as task
- Entry-point check
- Confirm before generating
- Where to write
myagents task create-from-alignment <alignmentSessionId> --name "<短任务名>"
What does the task-alignment skill do?
Alignment conversation starting from a 想法/idea. Co-decides with the user whether the idea should be acted on directly in the current session, or fixed into a formal Task for independent dispatch (one-off or recurring). Handles lightweight 'do it now while we talk', heavyweight 'define precisely, run later or on a schedule', and 'just help me think about this' — all on the same skill. Use when the user arrives via the 想法 panel's 'AI 讨论' button (parameter dictionary in the first message), or says 'let's think this through', 'help me plan this', 'I want to explore X', 'I have an idea', '/task-ali
How do I install it?
Run `npx skills add hAcKlyc/MyAgents --skill task-alignment --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From hAcKlyc/MyAgents, a repository with 847 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.