Verified:GitHub

technical-planning

Draft the Technical Plan section for the /plan Technical stage.

1|Updated Jan 22, 2026

Search Tags:#architecture #technical planning #risk assessment #decision log #integration points #engineering execution #NFR alignment

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It converts a feature’s intent (design and constraints) into an actionable technical plan that fits the existing codebase, so engineering can implement with fewer surprises and clearer integration boundaries.

Core Features & Use Cases

Technical Plan Intro drafting: produces a plain-language intro (1–3 paragraphs) that explains what changes, why they fit, and which components/data flows are touched.
Explicit integration mapping: identifies named interfaces, APIs, and data contract touchpoints, plus concrete architecture changes and sequencing.
Execution safety guardrails: lists failure modes per integration point, states invariants/non-changes, aligns NFRs, and updates risks/assumptions/tests with open questions where evidence is missing.

Quick Start

Ask the skill to draft the Technical Plan section for the /plan Technical stage using your Problem Definition, Challenge Artifacts, Context Snapshot, and any listed Constraints, NFRs, and decision log.

Frequently Asked Questions about technical-planning

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

FAQPage Schema

How do I convert feature intent into a technical plan tied to my existing codebase?▼

To convert feature intent into a technical plan, you draft a Technical Plan section that maps architecture changes, identifies integration points, and aligns NFRs with the current codebase. This approach produces an actionable plan with explicit execution boundaries and failure modes.

What is the best way to map integration points and failure modes during technical planning?▼

The best way to map integration points and failure modes is to explicitly identify named interfaces, APIs, and data contract touchpoints. You then list specific failure modes per integration point and state invariants to establish execution safety guardrails for engineering teams.

How do I draft a technical plan that aligns with non-functional requirements?▼

To draft a technical plan aligned with non-functional requirements, you map architecture changes and integration points against your listed NFRs. This alignment ensures the technical approach explicitly addresses execution safety, updates associated risks, and flags open questions where evidence is missing.

Can I update risks, assumptions, and tests while generating an architecture decision log?▼

Yes, you can update risks, assumptions, and tests while preserving decision log integrity during technical planning. The process generates the exact Technical Plan section content while simultaneously updating these execution safety guardrails to reflect new architectural changes.

What do I need to provide to generate a technical plan for an implementation scenario?▼

You need to provide your Problem Definition, Challenge Artifacts, Context Snapshot, and any listed Constraints, NFRs, and decision log. These inputs supply the feature intent, design constraints, and codebase context required to map integration points and draft the technical approach.