plan-work

Plan a forward-only DAG from an approved feature chunk into an EDN plan file.

5|3|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/leifericf/agentic-sdk --skill plan-work-leifericf
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-work
Source: https://github.com/leifericf/agentic-sdk/tree/main/skills/plan-work
Command: npx skills add https://github.com/leifericf/agentic-sdk --skill plan-work-leifericf

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the decomposition of approved feature plan chunks into a directed acyclic graph of phases and tasks, providing a summary to guide further action.

Core Features & Use Cases

  • Automated Planning: Generate phase and task summaries for approved feature chunks without manual decomposition.
  • Task and Phase Summary: Outputs the structure of each phase and task with their dependencies, along with a critical path for the plan.
  • Use Case: For a project manager who needs to break down a complex feature into manageable stages for development teams, this Skill can automate the planning process, streamlining the task assignment.

Quick Start

Run the plan-work Skill with the approved chunk name and the project run slug, such as: 'plan-work "ChunkName" "project_run_slug".'

Frequently Asked Questions about plan-work

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

FAQPage Schema
How do I automate feature planning and break down a complex project into manageable stages?

Automated feature planning decomposes approved feature chunks into a directed acyclic graph of phases and tasks. This generates an EDN plan file with a critical path, providing a compact summary to guide development teams through task execution.

What is a forward-only DAG and how does it map project requirements to actionable steps?

A forward-only DAG maps project requirements to actionable steps by structuring phases and tasks in a directed acyclic graph without cycles. It identifies dependencies between tasks and outputs a critical path to sequence task execution.

How do I generate a task dependency analysis and critical path summary for a software development project?

Dependency analysis and critical path generation happen by running the plan automation process with an approved chunk name and project run slug. It outputs the structure of each phase and task alongside their dependencies for human review.

Do I need an approved feature chunk before I can start automated plan generation?

Yes, automated plan generation requires an approved feature chunk name and a project run slug as input. It uses these parameters to map the approved project requirements to actionable steps within the software development lifecycle.

Can I integrate plan automation within the broader software development lifecycle using the agentic-sdk framework?

Yes, plan automation utilizes the agentic-sdk framework for integration within the broader software development lifecycle. It automates the mapping of project requirements to actionable steps and writes the generated plan to an EDN plan file.

What are the limitations of using a forward-only DAG for project management and task decomposition?

A forward-only DAG limits task decomposition to acyclic dependencies, meaning it cannot model iterative loops or circular feedback within a single plan. It writes to an EDN plan file and is designed specifically for executing approved feature chunks.