use-zfeats
Plan large features by drafting step-by-step checklists in zfeats/*.md using - [ ] items, then implement and mark items done as - [x]. Use when breaking down or executing multi-step tech plans.
When & Why to Use This Skill
This Claude skill facilitates structured feature planning and execution through markdown-based checklists. It enables users to break down complex technical requirements into actionable, ordered steps, providing a persistent source of truth for progress tracking and ensuring systematic implementation of large-scale projects within the codebase.
Use Cases
- Feature Decomposition: Breaking down high-level product requirements into detailed, step-by-step technical checklists to ensure no critical components are missed during development.
- Execution Tracking: Maintaining a persistent 'source of truth' for project status by marking items as complete and adding notes, allowing for seamless context recovery across different work sessions.
- Complex Refactoring: Planning and executing multi-stage code migrations or architectural changes by defining a clear sequence of operations and verifying each step before proceeding.
| name | use-zfeats |
|---|---|
| description | Plan and execute complex features using markdown checklists. Use when the user asks to "plan a feature", "create a checklist", or "break down a task". |
| allowed-tools | Read, Write, Edit, Glob, Bash |
Use zfeats for plans
Instructions
- Create or open a zfeats markdown file named after the feature (kebab-case) under
zfeats/(e.g.,zfeats/new-feature.md). - At the top, add a short context/goal, then enumerate steps as checkbox lines only:
- [ ] step detail(no unchecked bullets without boxes). - Steps should be actionable, scoped, and ordered; avoid vague items. Split big steps until each can be finished in one go.
- When implementing, work from the checklist in order. After completing a step, immediately update the same file to
- [x] ...with any brief note if useful. - If new work is discovered, append new
- [ ]items; do not delete history unless invalid—strike or annotate instead. - Keep the checklist as the source of truth while coding; ensure code changes correspond to items and mark them done only after verification/tests for that step.
- When finished, ensure all planned items are
- [x]or explicitly documented as deferred.
Example prompts
- "为多平台支持写一份 zfeats 计划并开始执行"
- "把发送队列优化拆分为清单，完成第一步并勾选"
- "查看并更新 zfeats/msg-queue.md 的完成情况"