Plan next
Read project state and design docs, then create the next batch of Linear issues for a projectFrom its SKILL.md
npx -y skills add cliffren/swf --skill plan-nextAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
3.4 KB, as published. Nobody here has run it
Plan Next Issues
Analyze current project state and create the next batch of issues in Linear.
Input
$ARGUMENTS — project name. Required. If not provided, ask.
Workflow
-
Load project state:
- Read
docs/design.md— what needs to be built - Read
CLAUDE.md— current phase - Read recent ADRs — any recent design decisions
- Check Linear: completed issues (what's done), remaining Todo issues (what's planned)
- Check git log: recent changes
- Read
-
Identify the gap:
- What does the current phase require (from Linear milestones + design.md)?
- What's already done?
- What's already in Todo/In Progress?
- What's missing?
-
Suggest parallelizable work from later phases:
- Some work can start before its phase is "current":
- Phase 5 的 Methods 初稿 → 核心算法确定后(Phase 1 末期)就能写
- Phase 4 的部分图 → Phase 2 有结果后就能做
- Phase 5 的 Introduction → 文献调研做过就能起草
- Present these as optional: "以下任务可以提前做,比如等实验跑的间隙:"
- Mark these issues with their actual Phase milestone, not the current one
- Some work can start before its phase is "current":
-
Draft new issues:
- Default issue granularity: half-day to two-day effort (adjustable — user can ask for coarser or finer granularity)
- Smaller tasks can be combined into one issue with a checklist in the description
- Rule of thumb: if you'd want to see its status independently on the board, make it an issue; otherwise, make it a checklist item
- Include: title, description with clear acceptance criteria, labels (type + executor), milestone
- For dev tasks, reference the relevant section of design.md
- For experiment tasks, specify inputs/outputs/success criteria
-
Present to user:
## 规划:MyProject Phase 2 基于 design.md 和当前进度,建议新建以下 issues: 1. [dev, agent:codex] 实现 XX 模块的 benchmark 脚本 描述:... 2. [experiment, manual] 在数据集 A 上运行 benchmark 描述:... 3. [figures, agent:claude] 生成性能对比图 描述:... --- 可提前做(等实验间隙)--- 4. [writing, agent:claude] Methods 核心算法描述(Phase 5) 5. [figures, agent:claude] 已有 benchmark 结果可视化(Phase 4) 确认创建吗?你可以: - 合并:把几个相关的 issue 合成一个(细节放 checklist) - 拆分:把太大的 issue 拆成多个 - 修改:调整标题、描述、labels -
Create issues after user confirms:
- Create each issue in Linear with correct project, milestone, labels
- Report created issues with IDs and links
Status Usage
- Todo — confirmed work, will be done. All planned issues default to Todo.
- Backlog — tentative, not sure if needed. Use only when the issue is speculative:
- "可能需要 ablation study,看 reviewer 要求再定"
- "如果性能不够再考虑优化"
- In Progress — currently being worked on (set by
/swf:next) - Do NOT use Backlog as "queued but not started yet" — that's what Todo is for.
Notes
- Never create issues without user confirmation
- If the current phase looks complete, suggest moving to the next phase
- Suggest breaking large tasks into sub-issues if they exceed 2 days