implementation-plan

Generate structured implementation plans with dependency graphs and validation checkpoints.

Updated Jun 1, 2026
One-click install
npx skills add https://github.com/aurora-atoms/lattice --skill implementation-plan-aurora-atoms
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implementation-plan
Source: https://github.com/aurora-atoms/lattice/tree/main/skills/implementation-plan
Command: npx skills add https://github.com/aurora-atoms/lattice --skill implementation-plan-aurora-atoms

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the ambiguity and coordination overhead that occurs when moving from an approved ticket to actual development, ensuring that work is decomposed logically and risks are identified early.

Core Features & Use Cases

  • Work Decomposition: Breaks down complex tasks into user-visible slices and technical enablers.
  • Critical Path Mapping: Identifies dependencies, integration points, and parallel work streams to optimize delivery.
  • Use Case: When a feature spans multiple modules and requires coordination between several engineers, use this Skill to generate a structured plan that highlights unknowns and validation checkpoints before coding begins.

Quick Start

Use the implementation-plan skill to generate a detailed execution roadmap for the current feature delivery case based on the provided system architecture and scope.

Frequently Asked Questions about implementation-plan

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

FAQPage Schema
How do I decompose a complex software engineering ticket into actionable delivery plans?

Work decomposition breaks down complex tasks into user-visible slices and technical enablers. It maps dependencies and integration points to optimize parallel work streams, ensuring logical breakdown and early risk identification before development begins.

What is critical path analysis in software delivery and when do I need it?

Critical path analysis identifies dependencies, integration points, and parallel work streams to optimize delivery. You need it when a feature spans multiple modules and requires coordination between several engineers to highlight unknowns before coding begins.

How do I map dependencies and identify risks for multi-module feature coordination?

Map dependencies and identify risks by generating a structured execution roadmap based on system architecture. This defines validation checkpoints and highlights unknowns, preserving developer authority while reducing coordination overhead during engineering workflows.

Does structured implementation planning preserve developer authority over the engineering workflow?

Structured implementation planning preserves developer authority over the engineering workflow. It satisfies requirements for explicit dependency mapping and evidence-based planning while ensuring work decomposition identifies risks early without overriding technical decisions.

What is the best way to define validation checkpoints before coding begins?

The best way to define validation checkpoints before coding begins is to apply evidence-based planning to the feature delivery case. This generates an execution roadmap highlighting integration points and unknowns across technical enablers to optimize delivery.