design-plan-docs

Generate layered design documents with architecture, milestones, and BDD test plans.

Updated Nov 18, 2025
One-click install
npx skills add https://github.com/cajias/claude-skills --skill design-plan-docs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-plan-docs
Source: https://github.com/cajias/claude-skills/tree/main/plugins/dev-process/skills/design-plan-docs
Command: npx skills add https://github.com/cajias/claude-skills --skill design-plan-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you turn a vague project idea or feature request into a structured set of design documents that clarify intent, architecture, implementation sequencing, and test strategy before coding begins.

Core Features & Use Cases

  • Project intent framing: Defines the north star, tenets, and measurable success criteria for a project.
  • Layered design articulation: Produces logic design, structural design, implementation plan, and BDD test plan as separate documents with clear traceability.
  • Planning for execution: Organizes work into milestone-based plans that support disciplined implementation and validation.
  • Use case: A team is starting a non-trivial feature and wants a complete design package that can be reviewed and approved before any code is written.

Quick Start

Ask me to generate the full design document set for your feature or project.

Frequently Asked Questions about design-plan-docs

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

FAQPage Schema
What is a design document package for software architecture planning?

A design document package is a structured set of layered artifacts clarifying project intent, logical architecture, milestone sequencing, and BDD validation before implementation begins. It ensures traceable execution for non-trivial features.

How do I create an implementation plan with milestones and BDD test plans?

You create an implementation plan by structuring milestone-based execution sequencing alongside behavior-first test preparation. This generates separate documents for structural layout planning and BDD-oriented validation design to guide disciplined coding.

When do I need a C4-style logical architecture layout for my project?

You need a C4-style logical architecture layout when planning non-trivial features requiring clear structural design and traceable intent before coding. It articulates layered logic design to support disciplined review and approval.

Does this approach support behavior-first test preparation for feature planning?

Yes, this approach supports behavior-first test preparation by generating BDD-oriented validation design as a distinct layer. It integrates test strategy directly into the milestone-based execution plan before implementation starts.

What is the best way to frame project intent before writing any code?

The best way to frame project intent is to define the north star, core tenets, and measurable success criteria upfront. This transforms vague feature requests into a structured design document with traceable architecture.

Can I use this for non-trivial feature planning without external dependencies?

Yes, you can use this for non-trivial feature planning without external dependencies. It generates a complete design package including logic design, structural layout, and milestone sequencing entirely from your traceable project intent.