task-start
legacy fixture skill
- License 许可
- MIT
- 最近更新
- 2026-07-18
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- task-start
- description
- legacy fixture skill
03 SKILL.md 正文
Legacy Task Start
04 同仓库更多 Skills
ticket-incubate
Use to turn an idea that has no issue/ticket yet into an actionable GitHub issue. Grow a vague notion by divergence, narrow only the gaps via a deficit-based interview, and create the issue once the four required elements (background, goal, done criteria, out-of-scope) are filled. Triggers on "I have an idea", "let's make this a ticket", "create an issue", "interview me", or describing something to make/fix/improve without an issue number, even if the user never says the word "ticket". It is the front of the workbench lifecycle (idea -> ticket-incubate -> issue -> task-start). Distinct from brainstorming/design skills: those work out the how of what to build now; this captures the what of later work as a well-honed ticket.
task-tickets
Use to scan open workbench tickets joined with task branches and lifecycle events into unstarted / claim-attempted / in-progress / awaiting-PR / cleaned-up states. Read-only.
task-submit
Use when the user asks to submit, wrap up, or extract from a task, or when work has reached a point to open a PR.
task-status
Use to see local and remote task status at a glance and diagnose drift (unpushed, stale status, missed cleanup). When you want to know where everything stands before starting or submitting, or after a multi-device handoff.
task-start
Use when the user asks to start a task, pick up an issue, or begin a new attempt, or hands over an issue number to start work.
task-done
Use when the user asks to clean up or discard a task, or to clear the workspace after a PR is merged.