ce:work-beta

Execute work plans end-to-end by parsing plan documents and orchestrating tasks, tests, and reviews.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates end-to-end execution of work plans by interpreting plan documents and orchestrating tasks, tests, and reviews, enabling teams to ship features quickly with consistent governance.

Core Features & Use Cases

  • Interpret and execute work plans (plans, specifications, or todos) end-to-end, following a structured Execution Workflow to deliver complete features.
  • Optional external delegation via Codex to conserve tokens and accelerate coding tasks, with safeguards to prevent credential leakage and to pass auth through environment variables.
  • Track progress, enforce testing and linting, and produce incremental commits in alignment with plan units.
  • Use across plan-driven development workflows, from discovery through verification, QA, and deployment.

Quick Start

Provide a work plan file to ce:work-beta and the skill will execute it end-to-end.

Frequently Asked Questions about ce:work-beta

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

FAQPage Schema
How do I automate work plan execution for software development?

Automating work plan execution involves parsing plan documents and orchestrating tasks, tests, and reviews end-to-end. It executes development plans incrementally, ensuring changes are tested, linted, and validated before shipping.

Can I delegate coding tasks to Codex to conserve tokens?

Yes, you can delegate coding tasks to Codex to conserve tokens and accelerate execution. Delegation includes safeguards to prevent credential leakage by passing authentication through environment variables.

What is plan-driven development workflow automation?

Plan-driven development workflow automation interprets specification or todo documents to orchestrate feature rollouts. It tracks progress, guards against ambiguity, and produces incremental commits aligned with plan units.

How do I execute a specification document end-to-end?

Executing a specification document end-to-end requires providing the plan file to the skill. It parses the document, implements execution steps sequentially, and validates changes through automated testing and linting before shipping.

Does automated task management work without external dependencies?

Yes, automated task management works without external dependencies. External delegation via Codex is optional and applied only when token conservation matters during coding tasks within the execution workflow.

Why guard against ambiguity when executing development plans?

Guarding against ambiguity when executing development plans prevents incorrect task execution and failed tests. The skill enforces structured execution workflows to ensure changes are validated, linted, and aligned with plan units before shipping.