Verified:GitHub

plan

Create or update markdown plan artifacts through validated planning gates.

1|Updated Jan 22, 2026

Search Tags:#planning #workflow orchestration #decision log #validation gates #implementation readiness #GitHub projects #automation decomposition

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you reliably create or progress a high-quality implementation plan by enforcing deterministic gate checks, structured decision logging, and substance-first human review so plans don’t advance based on missing or vague requirements.

Core Features & Use Cases

Authoring-artifact lock: selects and echoes the correct plan markdown file before writing, preventing accidental edits to the wrong document.
Deterministic stage progression: advances through Problem → Feature → Technical → Human Readability → Implementation → Automation (optional) → Reviews with named validators.
Inline Q/A to remove ambiguity: runs targeted questions when gates fail or critical substance checkpoints are incomplete, aiming for zero-interaction implementer readiness.

Quick Start

Use /plan with your goal and hard constraints, and reference the plan file you want to update so it can be selected as the authoring artifact.

Frequently Asked Questions about plan

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

FAQPage Schema

How do I create an implementation plan with validation gates to prevent missing requirements?▼

Implementation plan creation with validation gates enforces deterministic stage progression from problem definition to review readiness. It uses named validators and structured decision logging to ensure plans do not advance based on vague or missing requirements.

What is the stage progression for authoring a technical plan through validated gates?▼

Technical plan stage progression advances deterministically through Problem, Feature, Technical, Human Readability, Implementation, optional Automation, and Reviews. Each stage contains named validators that block progression until substance checkpoints are fully satisfied.

How do I update an existing markdown plan file without accidentally editing the wrong document?▼

Updating an existing markdown plan file requires an authoring-artifact lock that selects and echoes the correct target document before writing. This prevents accidental edits to the wrong file when progressing partially completed plans through implementation.

Can I break down project automation tasks during the planning workflow?▼

Project automation task breakdown is supported as an optional stage after implementation readiness. Automation decomposition progresses planning through workflow orchestration, allowing you to define automated tasks before entering the final review gate.

What happens when a planning gate fails due to incomplete evidence or ambiguity?▼

When a planning gate fails due to incomplete evidence, inline Q/A runs targeted questions to remove ambiguity. This zero-interaction standard ensures implementers receive fully clarified requirements before the plan reaches review readiness.

Does workflow orchestration planning support continuing partially completed plans?▼

Workflow orchestration planning supports continuing partially completed plans through approval re-entry and freshness-aware reviews. It enforces deterministic gate order while allowing registry-first updates to progress existing markdown artifacts toward implementation.