architect:plan

Generate detailed implementation plans for software features in Markdown.

Updated Feb 24, 2026
One-click install
npx skills add https://github.com/atournayre/claude-personas --skill architect-plan-atournayre
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architect:plan
Source: https://github.com/atournayre/claude-personas/tree/main/architect/skills/plan
Command: npx skills add https://github.com/atournayre/claude-personas --skill architect-plan-atournayre

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the creation of detailed, actionable implementation plans for software features, ensuring all architectural decisions and tasks are clearly defined before development begins.

Core Features & Use Cases

  • Automated Plan Generation: Creates structured Markdown plans based on feature descriptions, clarification decisions, and chosen architecture.
  • Task Breakdown: Defines specific implementation steps and associated files.
  • Use Case: After defining a new feature and its architecture, use this Skill to generate a comprehensive plan that guides the development team through each implementation and testing phase.

Quick Start

Use the architect:plan skill to generate the implementation plan for the current feature.

Frequently Asked Questions about architect:plan

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

FAQPage Schema
How do I generate a detailed implementation plan for a software feature?

To generate an implementation plan, provide the feature description and prior architectural decisions. The plan outlines actionable steps, file specifications, and test definitions, storing the documentation in `docs/specs/`.

What is the best way to break down software development tasks into actionable steps?

Breaking down software tasks is done by defining specific implementation steps and associated files. This ensures the development team has clear, actionable guidance through each implementation and testing phase.

Can I automatically create directory setups and task documentation for new features?

Yes, automatic mode supports task creation and directory setup. It generates structured Markdown plans and documents them directly in `docs/specs/` without requiring manual file configuration.

Do I need defined architectural decisions before creating software implementation plans?

Yes, architectural decisions and feature descriptions are required inputs. The generated implementation plans are built based on these prior decisions to ensure alignment before development begins.

Does the plan generation process include test definitions for the new architecture?

Yes, the generated implementation plans include test definitions. This ensures that actionable steps and file specifications are paired with testing requirements for comprehensive development guidance.