Creates or resumes structured ExecPlan documents to guide feature delivery end-to-end.
npx skills add https://github.com/NeonTowel/oh-my-taskfiles --skill exec-plan
Please help me install this Agent Skill. Skill: exec-plan Source: https://github.com/NeonTowel/oh-my-taskfiles/tree/main/dotfiles/crush/skills/exec-plan Command: npx skills add https://github.com/NeonTowel/oh-my-taskfiles --skill exec-plan
This skill provides a self-contained ExecPlan document that guides a feature's delivery from design to verification, enabling novices to implement work end-to-end within the repository.
To begin, create a new ExecPlan Markdown file under .ai/plans/ (for example .ai/plans/feature-x.md) and start documenting the feature in the sections described. If you need to store temporary research or clones, put them in .ai/plans/tmp (gitignored).
High-intent search queries and answers about installing and using this skill.
To create a living document for feature delivery, you generate a structured ExecPlan Markdown file that records goals, milestones, a decision log, and outcomes in a single self-contained file. This document guides a coding agent to deliver a feature end-to-end while keeping all context in one place.
The best way to guide a coding agent end-to-end is using an ExecPlan, a self-contained document that defines explicit terms and observable outcomes. It enforces structured sections for progress, surprises, decisions, and validation steps to ensure verifiable feature delivery.
You resume an ongoing feature plan by reopening the existing ExecPlan document, which facilitates back-and-forth clarification and iteration between a product owner and developer. The living document retains all prior context, milestones, and decisions for seamless continuation.
You should store temporary research files or clones in the .ai/plans/tmp directory, which is gitignored. The actual ExecPlan living document itself should be created as a Markdown file under the .ai/plans/ directory.
Feature planning with an ExecPlan requires no specific frameworks or dependencies. It relies on creating a self-contained Markdown document that captures verifiable outcomes, milestones, and a decision log to guide the coding agent.
An ExecPlan living document requires specific sections for Progress, Surprises & Discoveries, Decision Log, and Outcomes. These sections enforce observability and validation by capturing milestones and clearly defined observable outcomes.
cshyangPlan and execute a project discovery phase to define requirements and scope.
RUSHYOPCoordinate AI agents with eval-first checks and cost-aware task routing.
bordenetTrack implementation progress across work sessions in a markdown document.
indrasvatCreate living execution plans with milestones, acceptance criteria, and decision logs.
