ce-work

Translate work plans into TodoWrite documents with dependencies and phase-based execution.

Updated Mar 12, 2026

Search Tags:#task-management #todowrite #software-engineering #project-management #quality-checks #incremental-commit #work-plans

Ready to run

npx skills add https://github.com/datorresb/discovery-event-platform --skill ce-work-datorresb

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ce-work
Source: https://github.com/datorresb/discovery-event-platform/tree/main/.github/skills/ce-work
Command: npx skills add https://github.com/datorresb/discovery-event-platform --skill ce-work-datorresb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Executives and engineers often struggle to translate vague plans into actionable tasks, leading to scope creep and delayed shipping. This skill bridges that gap by turning plan documents into a structured TodoWrite with clear dependencies and execution steps, enabling teams to finish features more reliably.

Core Features & Use Cases

Plan interpretation and TodoWrite generation that maps plan items to concrete tasks with dependencies.
Phase-based execution guidance, including environment setup, branch management, task execution, testing, and incremental commits.
Quality assurance and operating procedures, capturing testing, linting, and post-deploy validation requirements.

Quick Start

Feed your work plan document to the skill and it will generate a TodoWrite, create execution tasks, and initiate phase-based work.

Frequently Asked Questions about ce-work

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

FAQPage Schema

How do I translate a project plan into executable tasks with dependency tracking?▼

Incremental commits during phase-based execution maintain code stability by committing small, tested changes iteratively. This approach enforces quality gates and linting at each step, preventing integration conflicts and ensuring the final feature deployment remains stable.

What is phase-based execution for software engineering projects?▼

Post-deploy validation planning defines specific testing and quality assurance procedures executed after feature release. It captures testing, linting, and validation requirements to verify the deployed feature operates correctly in production environments, ensuring end-to-end task execution success.

How do I manage scope creep when delivering software features from vague plans?▼

To enforce quality checks during task execution, apply automated testing and linting procedures at each phase before incremental commits. This structured quality assurance approach captures validation requirements within the task breakdown, preventing defects from propagating through subsequent execution phases.

Does this approach work for software projects requiring iterative delivery?▼

To track task dependencies during feature development, generate a TodoWrite document that maps plan items to concrete tasks with clearly defined interdependencies. This structured tracking method enables iterative delivery by enforcing phase-based execution and preventing scope creep.