skills.rest
ships
shipsCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

engineering-planning

Creates dependency-ordered task lists with explicit verification criteria from engineering requests.

Updated Aug 23, 2026
Search Tags:#verification#task breakdown#acceptance criteria#implementation plan#engineering planning#dependency ordering#todo lists
One-click install
npx skills add https://github.com/ships/eden --skill engineering-planning
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: engineering-planning
Source: https://github.com/ships/eden/tree/main/assets/claude/skills/engineering-planning
Command: npx skills add https://github.com/ships/eden --skill engineering-planning

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Engineering planning often produces vague todo lists that are hard to execute and hard to verify, which leads to rework, unclear ownership, and incomplete outcomes.

Core Features & Use Cases

  • Concrete task definition: Turns goals into specific, observable actions with clear targets.
  • No-time-estimate planning: Helps teams avoid timeboxing in task descriptions to keep work definition focused on outcomes.
  • Actionable, testable outcomes: Ensures each item includes verification criteria so “done” is unambiguous.
  • Use Case: Break down a feature into models, API changes, frontend updates, validations, tests, and documentation in an order that respects dependencies.

Quick Start

Use this skill to create an execution-ready plan by turning your feature description into dependency-ordered, testable todo items without any time estimates.

Frequently Asked Questions about engineering-planning

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

FAQPage Schema
How do I break down software features into actionable engineering tasks?▼

Engineering task breakdown decomposes feature designs, bug fixes, or refactors into specific, observable actions ordered by component dependencies. This ensures each work item is self-contained with explicit completion conditions rather than a vague objective.

What is the best way to write acceptance criteria for a development todo list?▼

Acceptance criteria for development todo lists should define observable, testable outcomes that make "done" unambiguous. Each task must include explicit verification conditions without relying on vague wording or time estimates to guide execution.

Why do engineering implementation plans fail during execution?▼

Engineering implementation plans often fail when task lists contain vague wording and lack clear verification criteria. Without self-contained tasks ordered by dependencies, teams face rework, unclear ownership, and incomplete outcomes during execution.

How do I order todo items by component dependencies for a software refactor?▼

Ordering todo items by component dependencies requires decomposing refactors into models, API changes, and frontend updates sequentially. This ensures foundational changes are completed before dependent tasks, producing an execution-ready plan.

Can I include time estimates in engineering planning task descriptions?▼

Time estimates are explicitly forbidden in engineering planning task descriptions. Removing timeboxing keeps work definition focused strictly on outcomes and observable actions, ensuring tasks remain self-contained and execution-ready.

Related Skills

Explore More Software Engineering Skills→
BigdropsBigdrops
1

qa-test-planner

Generates QA documentation including test plans, cases, suites, bug reports, and Figma design validations.

Community
Advanced
machenjiemachenjie
4

failure-diagnosis

Diagnose software failures by separating symptom, trigger, and root cause.

Community
Advanced
hemoryhemory

daily-review

Track daily plan completion, meeting follow-ups, and next-day focus.

Community
Advanced
Omar-ObandoOmar-Obando
44

product-owner

Structure user stories and acceptance criteria for agile backlog refinement.

Community
Basic