use-zfeats

Plan and execute complex features using markdown checklists in zfeats files.

1|Updated Dec 5, 2025

Search Tags:#workflow #planning #markdown #checklist #feature

Ready to run

npx skills add https://github.com/lollipopkit/cc-skills --skill use-zfeats

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: use-zfeats
Source: https://github.com/lollipopkit/cc-skills/tree/main/use-zfeats
Command: npx skills add https://github.com/lollipopkit/cc-skills --skill use-zfeats

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps plan and manage complex features by converting ideas into structured markdown checklists stored under zfeats/.

Core Features & Use Cases

Checklist as Source of Truth: Create or open a zfeats markdown file, with context and a list of steps as - [ ] items.
Progress Tracking: Mark steps as - [x] as work is completed; append new tasks as needed.
Structured Execution: Steps are ordered and scoped; execution follows the checklist to completion.
Documentation: Maintains a living record of planning and execution.

Quick Start

Create or open zfeats/new-feature.md with a short context and a checklist using - [ ] for each task; update progress by marking - [x] upon completion.

Frequently Asked Questions about use-zfeats

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I break down a complex feature into actionable steps?▼

Create a markdown checklist by opening or creating a zfeats/<feature>.md file with a brief context statement followed by task steps formatted as - [ ] items. Each checkbox represents a discrete, ordered action; mark items as - [x] when completed to track progress through the entire feature.

Can I use markdown checklists to plan and track feature development?▼

Yes. Markdown checklists serve as the source of truth for feature planning and execution. Store them in zfeats/ as .md files, update checkboxes as work progresses, and append new - [ ] tasks as you discover additional work during implementation.

How do I update my feature checklist as I complete tasks?▼

Mark completed steps with - [x] and add new discovered tasks as - [ ] lines. The checklist remains the authoritative record; update it after verifying each step works, keeping the file synchronized with actual code changes and testing progress.

What's the best way to organize feature planning in a development workflow?▼

Structured markdown checklists in a dedicated zfeats/ directory provide both planning scaffolding and living documentation. Ordering steps logically and treating the checklist as binding guidance ensures features are executed methodically rather than ad hoc.

Do I need special tools to create and maintain feature checklists?▼

No. Feature checklists use plain markdown syntax and standard - [ ] checkbox formatting, requiring only a text editor. Store files in kebab-case under zfeats/ and update them as work progresses without additional dependencies.