task-execution-engine
Execute implementation tasks from design documents using markdown checkboxes. Use when (1) implementing features from feature-design-assistant output, (2) resuming interrupted work, (3) batch executing tasks. Triggers on 'start implementation', 'run tasks', 'resume'.
- License 许可
- MIT
- 最近更新
- 2026-11-11
- Stars
- ★ 3.3w
- Forks
- 3.9k
01 前言 Front Matter
- name
- task-execution-engine
- description
- Execute implementation tasks from design documents using markdown checkboxes. Use when (1) implementing features from feature-design-assistant output, (2) resuming interrupted work, (3) batch executing tasks. Triggers on 'start implementation', 'run tasks', 'resume'.
02 资源文件 3
- 参考文档references/task-format.md2.4 KB
- 参考文档references/workflow-guide.md3.9 KB
- 脚本scripts/task_manager.py13.5 KB
03 SKILL.md 正文
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 endpoint
See 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. CONTINUE
Unattended 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 implemented
Failed task:
- [x] **Create User model** `priority:1` `phase:model` ❌
- files: src/models/user.py
- [ ] User model has email field
- reason: Missing database configuration
Resume / Recovery
To resume interrupted work, simply run again with the same design file:
/feature-pipeline docs/designs/xxx.md
The 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 task-execution-engine]
04 同仓库更多 Skills
wealthville-pool-scoring
Score DeFi liquidity pools before providing liquidity. Returns a 0-100 pool score and an Enter/Hold/Exit/Reduce/Avoid verdict with calibrated confidence for ~68,800 Solana pools and 575 EVM pools, plus a public miss-inclusive track record. Use when asked whether a pool is worth LPing into, which pools look best right now, or how accurate the scores have actually been.
technical-debt-auditor
Scans a codebase and produces a quantified technical debt report with a prioritized remediation plan. Analyzes dead code, TODO/FIXME/HACK markers, dependency staleness, complexity hotspots, code duplication signals, test coverage gaps, unused exports, and outdated patterns. Use this skill when the user asks to audit their codebase for tech debt, wants a health check of their code quality, says things like "where should I focus refactoring", "find code smells", "audit my codebase", "what technical debt do we have", "prioritize cleanup work", or asks about code quality metrics. Also trigger when the user mentions "code rot", "legacy cleanup", "refactoring priorities", or wants to understand the overall health of a project before a major effort. Trigger even if the user doesn't say "technical debt" explicitly — any request to systematically assess code quality and identify improvement priorities belongs here.
readonly-sql-guard
Make an agent's database access provably read-only. Use when an agent runs caller-supplied SQL against a production/ERP/analytics database (a "query" MCP tool, text-to-SQL, an admin console), or when reviewing DB-access code for write/DDL/side-effect/transaction-escape risks. Checks what a statement CALLS, not just its shape.
web-artifacts-builder
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
discernment-nudge
After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.