ce:work

Automate end-to-end execution of work plans with quality checks and incremental commits.

6|Updated Jan 29, 2023
One-click install
npx skills add https://github.com/rethinkhealth/glion --skill ce-work-rethinkhealth
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ce:work
Source: https://github.com/rethinkhealth/glion/tree/main/.agents/skills/ce-work
Command: npx skills add https://github.com/rethinkhealth/glion --skill ce-work-rethinkhealth

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Executing work plans in complex projects is error-prone and slow without a structured workflow. This Skill provides a repeatable process to translate plans into tasks, manage dependencies, and enforce quality checks so features ship reliably.

Core Features & Use Cases

  • Translate a plan into actionable tasks and guide setup, execution, and verification phases.
  • Respect Execution notes and dependencies to ensure correct sequencing, scoping, and risk management.
  • Support incremental commits and a post-deploy validation outline to ensure robust releases.

Quick Start

Provide a work plan file (plan.md or plan.json) to begin execution.

Frequently Asked Questions about ce:work

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

FAQPage Schema
How do I automate work plan execution and task breakdown for software projects?

Automating work plan execution requires translating plans into actionable tasks, managing dependencies, and enforcing quality checks. This process guides setup, execution, and verification phases to ensure features ship reliably through incremental commits.

What is the best way to manage dependencies and execution notes in a project work plan?

Managing dependencies and execution notes involves reading specific guidance from your plan files to ensure correct task sequencing and risk management. This structured workflow respects existing notes to scope tasks properly and prevent execution errors.

How do I enforce quality assurance and post-deploy validation during feature releases?

Enforcing quality assurance and post-deploy validation requires applying automated quality checks and reading validation outlines from your work plans. This ensures robust releases by verifying features incrementally before and after deployment.

Can I execute work plans from markdown or JSON files for incremental commits?

Yes, you can execute work plans by providing a markdown or JSON plan file. The system reads execution notes, dependencies, and validation guidance from these files to automate task creation and guide incremental commits.

Why does complex project execution fail without a structured task management workflow?

Complex project execution fails without a structured workflow because translating plans into tasks becomes error-prone and slow. A repeatable process enforces necessary quality checks, dependency sequencing, and incremental commits to ship features reliably.

Does this work plan execution approach support post-deploy validation and testing phases?

Yes, this approach supports testing and post-deploy validation phases. It reads post-deploy validation guidance directly from your work plans and applies quality checks throughout the execution strategy to ensure timely feature completion.