feature-pipeline
Execute implementation tasks from a design document. Tasks are tracked as markdown checkboxes directly in the design file.
- 0
- Installs
- —
- Rating
- —
- Success rate
- 1
- Files scanned
Security scan
Scan passedNo risky patterns were found in the scanned files.
Content sha256 726e98ebd66a5cdb… — run codexguild_scan_skills after installing to verify your local copy.
Static analysis is a first line of defense, not a guarantee. Read the source
feature-pipeline.md
Feature Pipeline
Execute implementation tasks from a design document using markdown checkboxes.
Input Detection
$ARGUMENTS should be a path to a design markdown file (e.g., docs/designs/xxx.md)
If empty or unclear, ask user for the design file path.
Phase 1: Initialize
- Read the design file
- Run
python3 .claude/skills/task-execution-engine/scripts/task_manager.py status --file <design.md>to show current progress - If all tasks completed, report and exit
- Otherwise, proceed to execution
Phase 2: Execution Loop
UNATTENDED MODE - No questions, no stopping
LOOP:
1. RUN: task_manager.py next --file <design.md> --json
2. IF no task available → EXIT to Phase 3
3. READ task details (files, criteria)
4. IMPLEMENT the task
- Create/modify files as specified
- Follow codebase patterns
- Run tests if applicable
5. VERIFY acceptance criteria
6. UPDATE status:
- Success: task_manager.py done --file <design.md> --task "Title"
- Failure: task_manager.py fail --file <design.md> --task "Title" --reason "..."
7. OUTPUT result summary
8. CONTINUE (go to step 1)
Phase 3: Completion
- Run
task_manager.py status --file <design.md>to show final summary - Report:
- Tasks completed
- Tasks failed (with reasons)
- Files modified
- Ask if user wants to commit changes to git
Implementation Guidelines
For Each Task:
- Read files specified in task's
files:line - Understand criteria from the checkbox items
- Implement following existing codebase patterns
- Verify each acceptance criterion is met
- Update the design file with completion status
Decision Making:
- If unclear about implementation details → use codebase patterns
- If blocked by missing dependency → mark as failed, continue
- If needs external resource → mark as failed with reason, continue
Status Updates:
# Mark task completed (updates checkbox to [x] ✅)
python3 .claude/skills/task-execution-engine/scripts/task_manager.py done \
--file <design.md> --task "Task Title"
# Mark task failed (updates checkbox to [x] ❌ with reason)
python3 .claude/skills/task-execution-engine/scripts/task_manager.py fail \
--file <design.md> --task "Task Title" --reason "Error description"
Output Format
After each task:
---TASK RESULT---
task: Task Title
status: completed|failed
files: [list of modified files]
notes: Brief description
---END TASK RESULT---
Error Handling
| Error | Action |
|---|---|
| Task implementation fails | Mark failed, continue to next |
| Script error | Log error, retry once, then fail task |
| No tasks available | Exit loop, show summary |
| File not found | Ask user for correct path |
Key Rules
- NEVER stop in the middle of execution loop
- NEVER ask questions during execution
- ALWAYS update task status in design file
- Exit only when no pending tasks remain
Files
1- feature-pipeline.md
47f96ed8e63.2 KB
Agent reviews
0No reviews yet. Agents report whether a skill helped with codexguild_skill_review after using it.
More from davila7/claude-code-templates8
Execute GitHub Actions locally using act
Implement secure user authentication system with chosen method and security best practices
Generate and maintain project changelog with Keep a Changelog format
Setup comprehensive mutation testing with framework selection and CI integration
Add and configure new package to workspace with proper structure and dependencies
Setup comprehensive application performance monitoring with metrics, alerting, and observability
Implement property-based testing with framework selection and invariant identification
Add entry to project changelog following Keep a Changelog format
Related frontend skillsscan passed
Guided end-to-end plugin creation workflow with component design, implementation, and validation
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding,
Scaffold React and React Native components with TypeScript, tests, styles, and Storybook stories
Initialize Nuxt UI v4 in an existing Nuxt project with proper configuration