skills.rest
TK-Evans01
TK-Evans01COMMUNITY
Explore all skills by this author →
GitHub

writing-design-plans

Create structured design plans with architecture, phases, and acceptance criteria.

Updated May 7, 2026
Search Tags:#implementation planning#software development#acceptance criteria#structured documentation#design plans
One-click install
npx skills add https://github.com/TK-Evans01/tk-harness --skill writing-design-plans-tk-evans01
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-design-plans
Source: https://github.com/TK-Evans01/tk-harness/tree/main/plugins/tk-rpie/skills/writing-design-plans
Command: npx skills add https://github.com/TK-Evans01/tk-harness --skill writing-design-plans-tk-evans01

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of creating and validating design plans, ensuring they are well-structured, comprehensive, and ready for implementation.

Core Features & Use Cases

  • Design Document Creation: Append validated design to existing documents with structured format.
  • Summary and Glossary Generation: Automatically create Summary and Glossary sections.
  • Acceptance Criteria Validation: Inline generation and validation of Acceptance Criteria.
  • Implementation Phases: Break design into discrete phases for manageable implementation.
  • Use Case: Ideal for software development projects where clear design plans are crucial for successful implementation.

Quick Start

Use the writing-design-plans skill to append a design plan for a new feature to the existing document 'feature-x-design.md'.

Frequently Asked Questions about writing-design-plans

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

FAQPage Schema
How do I create structured design plans for software development projects?▼

Create structured design plans by automating document generation with architecture, patterns, implementation phases, and inline acceptance criteria validation.

What is the best way to break down software implementation into discrete phases?▼

Break down implementation by generating discrete phases within design plans, ensuring manageable execution and comprehensive content validation.

How do I generate and validate acceptance criteria during design document creation?▼

Generate and validate acceptance criteria inline during design document creation, ensuring structured format and comprehensive content for software projects.

Can I append a new design plan to an existing markdown document?▼

Yes, append validated design plans to existing markdown documents while automatically generating Summary and Glossary sections for context.

Does this design planning approach require collaboration with other subagents?▼

Yes, the design planning approach requires collaboration with other subagents for context gathering and validation, adhering to house-style guidelines.

When do I need structured documentation for implementation planning?▼

Need structured documentation when software development projects require clear design plans with discrete implementation phases and validated acceptance criteria for successful execution.

Related Skills

Explore More Software Engineering Skills→
ovachieverovachiever
52

tailwind-v4-shadcn

Set up Tailwind v4 with shadcn/ui in Vite React projects.

Community
Advanced
SeaBrad72SeaBrad72
1

design

Enforce design-first approval gates before code generation in agentic development.

Community
Advanced
DaBigHomieDaBigHomie
1

maximus-prime-doc-validation

Chain existing validators to return a PASS/FIX verdict for Maximus Prime documentation.

Community
Advanced
ayubunayubun
8

writing-design-plans

Automates creation of software design documents with structured phases and summary/glossary generation.

Community
Advanced