Verified:GitHub

implementation-planning

Draft an execution-ready implementation plan with file deltas, workstreams, gates, and exit criteria.

1|Updated Jan 22, 2026

Search Tags:#implementation planning #workstreams #deployment rollback #CI gates #file ownership #test matrix #automation decomposition

Ready to run

npx skills add https://github.com/Atlas-Memory-Framework/AtlasMemory-Tools --skill implementation-planning-atlas-memory-framework

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: implementation-planning
Source: https://github.com/Atlas-Memory-Framework/AtlasMemory-Tools/tree/main/.cursor/skills/implementation-planning
Command: npx skills add https://github.com/Atlas-Memory-Framework/AtlasMemory-Tools --skill implementation-planning-atlas-memory-framework

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of turning a high-level implementation intent into a detailed, execution-ready plan with explicit file deltas, workstreams, gates, and evidence-based exit criteria—so downstream build agents can execute without prior context.

Core Features & Use Cases

Execution-ready plan drafting: Creates a full draft for the ## Implementation Plan section with file ownership, workstreams, phases, and tasks mapped to owners.
Safety and determinism guardrails: Enforces named gates (with where they run and what “green” means), a merge-point checklist, and explicit rollout/rollback triggers and steps.
Automation handoff compatibility: If an AutomationTarget is provided, includes stable IDs and boundaries so /automation-decomposition can derive one-PR leaf issues without inventing scope.

Quick Start

Use the implementation-planning skill to draft the ## Implementation Plan for your current plan artifact, including exhaustive file deltas, workstreams, gates with CI/local/deployed entrypoints, a minimal test matrix, and explicit rollout and rollback steps.

Frequently Asked Questions about implementation-planning

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

FAQPage Schema

How do I create an execution-ready implementation plan with file deltas and workstreams?▼

An execution-ready implementation plan requires exhaustive ownership-enforced file delta mapping, named workstreams, phases, and tasks mapped to owners so build agents can execute without user interaction.

What are CI gates and how do they work in implementation planning?▼

CI gates in implementation planning are named checkpoints with defined entrypoints for local, CI, and deployed environments, specifying exactly what constitutes a green or passing state to enforce safety and determinism.

How do I define deployment rollback triggers and steps for a build agent?▼

Defining deployment rollback steps involves specifying explicit rollback triggers and procedural steps within your implementation plan, ensuring build agents have deterministic safety guardrails during execution.

Does implementation planning work with automation decomposition handoffs?▼

Yes, implementation planning supports automation decomposition handoffs by providing stable IDs and boundaries for AutomationTargets, allowing downstream processes to derive one-PR leaf issues without inventing scope.

When do I need a test matrix and merge-point checklist for implementation planning?▼

A test matrix and merge-point checklist are required when drafting an execution-ready implementation plan to enforce safety guardrails and establish evidence-based exit criteria for each phase.