implementation-planning

Translate architecture outlines into executable task sequences with dependencies and risks.

86|9|Updated Jun 5, 2026
One-click install
npx skills add https://github.com/magnus919/hermes-profiles --skill implementation-planning-magnus919
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implementation-planning
Source: https://github.com/magnus919/hermes-profiles/tree/main/skills/implementation-planning
Command: npx skills add https://github.com/magnus919/hermes-profiles --skill implementation-planning-magnus919

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Transforms architecture into executable task sequences with explicit dependencies, risks, and rollback readiness, reducing ambiguity and delivery delays.

Core Features & Use Cases

  • Decompose architectures into estimable tasks to enable accurate planning.
  • Identify dependencies and the critical path to reveal scheduling risks.
  • Perform structured risk assessment and define rollback strategies for safe deployments.
  • Example use case: planning the rollout of a new service across teams with clear handoffs and milestones.

Quick Start

Provide your architecture outline and start the DECOMPOSE step to generate a task breakdown with dependencies and risk buffers.

Frequently Asked Questions about implementation-planning

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

FAQPage Schema
How do I break down software architecture into executable tasks with dependencies?

Work breakdown structures are created by translating architecture outlines into estimable task sequences with explicit dependencies and risk buffers. This decomposition clarifies what to do, when, and who is responsible for each phase.

What is the best way to identify the critical path and scheduling risks for a feature rollout?

Identifying the critical path requires mapping task dependencies and performing structured risk scoring. This reveals scheduling risks and defines rollback strategies to ensure safe deployments across cross-team initiatives.

How do I plan a rollback strategy for a cross-team service deployment?

Rollback strategies are planned by performing structured risk assessment during the task decomposition phase. This defines explicit rollback readiness for safe deployments and clarifies responsibilities across cross-team handoffs.

Can I use dependency analysis to estimate tasks for architectural refreshes?

Dependency analysis supports architectural refreshes by decomposing the design into estimable tasks. Identifying dependencies and the critical path reveals scheduling risks and clarifies work sequencing for accurate planning.

What do I need to start planning a project phase with work breakdown and risk buffers?

To start planning, provide your architecture outline and begin the decomposition step. This generates a task breakdown with explicit dependencies, risk scores, and rollback strategies to guide execution.