eng-task-planning

Convert engineering plans and design documents into phased markdown task plans.

1|Updated Jun 7, 2024
One-click install
npx skills add https://github.com/jsco2t/dotfiles --skill eng-task-planning
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eng-task-planning
Source: https://github.com/jsco2t/dotfiles/tree/main/.claude/skills/eng-task-planning
Command: npx skills add https://github.com/jsco2t/dotfiles --skill eng-task-planning

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the conversion of high-level engineering plans and design documents into a concrete, prioritized, and time-estimated task plan that can be handed to a team of developers.

Core Features & Use Cases

  • Automatically generate an epic-level task breakdown with time estimates and a structure that supports parallel work.
  • Analyze feature research documents, Jira/Confluence, and source code to extract context, constraints, and acceptance criteria.
  • Produce a ready-to-implement task plan document (and optional Jira-ready tickets) organized into phases with dependencies and risk notes.
  • Use case: when given a new feature spec and architecture diagrams, the skill outputs a phased plan that minimizes bottlenecks and optimizes team throughput.

Quick Start

Provide the high-level engineering plan and design document; the skill will return an ordered, time-estimated task plan optimized for parallel work.

Frequently Asked Questions about eng-task-planning

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

FAQPage Schema
How do I break down an engineering plan into actionable tasks?

The skill transforms high-level engineering plans and design documents into a structured, executable task plan. It identifies tasks, dependencies, risks, and acceptance criteria, outputting a markdown document with a phased epic structure and time estimates.

Can I generate Jira tickets from a feature spec and architecture diagrams?

Yes, the skill produces a ready-to-implement task plan document and optional Jira-ready tickets. It organizes the output into phases with dependencies, acceptance criteria, and risk notes extracted from your design documents.

What is the best way to structure epics to maximize parallel work?

The best way to structure epics for parallel work is to analyze dependencies and constraints within your engineering plan. This skill outputs a phased plan that minimizes bottlenecks and optimizes team throughput by identifying tasks that can run concurrently.

Does the task planning process account for risk management and dependencies?

Yes, the task planning process accounts for risk management and dependencies. It analyzes feature research, Jira or Confluence references, and source code to extract constraints, identify risks, and map dependencies across multiple epics.

How do I estimate development time for a new feature spec?

To estimate development time for a new feature spec, the skill analyzes your design documents and source code. It generates a markdown task plan with time estimates for each task and a phased epic structure to maximize parallel work.