technical-design

Generate module-level technical design documents through a two-phase planning and writing workflow.

Updated Mar 13, 2026
One-click install
npx skills add https://github.com/hisuL/ProjectSkill --skill technical-design-hisul
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: technical-design
Source: https://github.com/hisuL/ProjectSkill/tree/main/technical-design
Command: npx skills add https://github.com/hisuL/ProjectSkill --skill technical-design-hisul

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines the creation of module-level technical design documents by orchestrating a two-phase process: first planning, then writing.

Core Features & Use Cases

  • Two-Phase Workflow: Ensures a structured approach by first generating a technical design plan and then producing the final documentation from that plan.
  • Compatibility Entry: Maintains backward compatibility for direct invocation of technical-design.
  • Use Case: When starting a new feature, use this Skill to guide the process from initial PRD and architecture documents to a complete technical design, ensuring all necessary planning steps are followed before final documentation is generated.

Quick Start

Use the technical-design skill to create a technical design plan from the PRD and architecture documents, then write the final module-level technical design documents from that plan.

Frequently Asked Questions about technical-design

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

FAQPage Schema
How do I generate module-level technical design documents from PRD and architecture docs?▼

To generate module-level technical design documents, this Skill orchestrates a two-phase workflow that first creates a structured planning artifact from your source PRD and architecture documents, then hands off that intermediate plan to a writer agent to produce the final documentation.

What is the two-phase planning and writing workflow for technical design?▼

The two-phase technical design workflow separates planning from writing: the first phase generates a technical design plan from source materials, and the second phase uses that structured intermediate artifact to produce comprehensive module-level documentation.

When do I need a structured workflow for module design documentation?▼

You need a structured workflow for module design documentation when starting a new feature and translating initial PRD and architecture documents into comprehensive technical design, ensuring all necessary planning steps are followed before final documentation is generated.

Can I skip the planning phase and directly invoke technical design writing?▼

Direct invocation of technical design writing is supported through a backward compatibility entry, but the recommended approach follows the full two-phase workflow to ensure the writer agent receives structured intermediate artifacts for comprehensive documentation.

What's the best way to structure technical design planning before writing documentation?▼

The best way to structure technical design planning is to use a dedicated planner agent that processes source materials into structured intermediate artifacts, managing the handoff to a writer agent to ensure the final documentation adheres to the defined workflow.