feature-pipeline
Skill340 starsChanged 9 months agoMITView on GitHub
Execute implementation tasks from design documents using markdown checkboxes. Use when (1) implementing features from feature-analyzer output, (2) resuming interrupted work, (3) batch executing tasks. Triggers on 'start implementation', 'run tasks', 'resume'.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- gaia-research/gaia-skill-treetheir own version, first seen Nov 7, 2026
- Shadysmetools/claude-super-workflowtheir own version, first seen Oct 15, 2026
- notedit/happy-coding-agentword for word, first seen Oct 8, 2026
- vikisingh23/neuraforge-aitheir own version, first seen May 4, 2026
Other versions4 projects use a version of this.
Word for word · 1
- notedit/happy-coding-agent★ 339100% same
Edited · 0
None found.
Wrote their own version · 3
- gaia-research/gaia-skill-tree★ 22same name
- vikisingh23/neuraforge-ai★ 4same name
- Shadysmetools/claude-super-workflow★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository12 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- feature-analyzerSkill
- feature-devSkill
- issue-flowSkill
- screenshot-analyzerSkill
- cover-imageSkill
- skill-creation-guideSkill
- tts-skillSkill
- gsap-animationSkill
- react-animationSkill
- spring-animationSkill
- video-producerSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 69
If blocked, mark as failed and continue
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Feature Pipeline
Execute implementation tasks directly from design documents. Tasks are managed as markdown checkboxes - no separate session files needed.
Quick Reference
# Get next task
python3 scripts/task_manager.py next --file <design.md>
# Mark task completed
python3 scripts/task_manager.py done --file <design.md> --task "Task Title"
# Mark task failed
python3 scripts/task_manager.py fail --file <design.md> --task "Task Title" --reason "..."
# Show status
python3 scripts/task_manager.py status --file <design.md>Task Format
Tasks are written as markdown checkboxes in the design document:
## Implementation Tasks
- [ ] **Create User model** `priority:1` `phase:model`
- files: src/models/user.py, tests/models/test_user.py
- [ ] User model has email and password_hash fields
- [ ] Email validation implemented
- [ ] Password hashing uses bcrypt
- [ ] **Implement JWT utils** `priority:2` `phase:model`
- files: src/utils/jwt.py
- [ ] generate_token() creates valid JWT
- [ ] verify_token() validates JWT
- [ ] **Create auth API** `priority:3` `phase:api` `deps:Create User model,Implement JWT utils`
- files: src/api/auth.py
- [ ] POST /register endpoint
- [ ] POST /login endpointSee references/task-format.md for full format specification.
Execution Loop
LOOP until no tasks remain:
1. GET next task (task_manager.py next)
2. READ task details (files, criteria)
3. IMPLEMENT the task
4. VERIFY acceptance criteria
5. UPDATE status (task_manager.py done/fail)
6. CONTINUEUnattended Mode Rules
- NO stopping for questions
- NO asking for clarification
- Make autonomous decisions based on codebase patterns
- If blocked, mark as failed and continue
Status Updates
Completed task:
- [x] **Create User model** `priority:1` `phase:model` ✅
- files: src/models/user.py
- [x] User model has email field
- [x] Password hashing implementedFailed task:
- [x] **Create User model** `priority:1` `phase:model` ❌
- files: src/models/user.py
- [ ] User model has email field
- reason: Missing database configurationResume / Recovery
To resume interrupted work, simply run again with the same design file:
/feature-pipeline docs/designs/xxx.mdThe task manager will find the first uncompleted task and continue from there.
Integration
This skill is typically triggered after /feature-analyzer completes:
User: /feature-analyzer implement user auth
Claude: [designs feature, generates task list]
Design saved to docs/designs/2026-01-02-user-auth.md
Ready to start implementation?
User: Yes / 开始实现
Claude: [executes tasks via feature-pipeline]Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

