basic-design-workflow

Generate and refine basic design documents from requirement specifications.

Updated Jan 8, 2026
One-click install
npx skills add https://github.com/takemo101/compose-workflow --skill basic-design-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: basic-design-workflow
Source: https://github.com/takemo101/compose-workflow/tree/main/.pi/skills/basic-design-workflow
Command: npx skills add https://github.com/takemo101/compose-workflow --skill basic-design-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the creation of basic design documents from requirements, ensuring technical completeness and adherence to architectural standards through an iterative review process.

Core Features & Use Cases

  • Automated Design Generation: Creates initial drafts of basic design documents based on input requirements.
  • Iterative Review & Refinement: Incorporates feedback from a quality assurance loop to meet a minimum score (9 points) before proceeding.
  • Technical Stack Validation: Ensures all necessary technical layers are considered and defined, prompting for user input on undefined areas.
  • Use Case: A product manager provides a requirements document for a new feature, and this Skill generates the foundational technical design, including architecture, technology stack, and data models, ready for detailed design.

Quick Start

Use the basic-design-workflow skill to generate a basic design document from the requirements file located at docs/requirements/REQ-001.md.

Frequently Asked Questions about basic-design-workflow

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

FAQPage Schema
How do I automate basic design document generation from requirements?

Automating basic design document generation from requirements involves parsing requirement specifications to draft architecture, technology stacks, and data models. This skill validates technical layers and uses an iterative review loop to ensure completeness before proceeding to detailed design.

What is the process for validating a technical stack during basic design?

Validating a technical stack during basic design requires checking requirement specifications against defined architectural standards. The process prompts for user input on undefined technical layers, ensuring all necessary technology stack components are explicitly defined before drafting.

How does iterative quality assurance work for technical documentation?

Iterative quality assurance for technical documentation uses an automated review loop that scores drafts against defined standards. The refinement cycle repeats until the document achieves a minimum score of 9 points, guaranteeing technical completeness before advancing to the next phase.

Can I integrate newly generated basic designs with existing software architecture?

Integrating newly generated basic designs with existing software architecture is supported during the drafting phase. The workflow validates technical layers and incorporates user-driven technical clarifications to seamlessly merge new requirement specifications with existing design documents.

Do I need predefined requirement specifications to generate a basic design?

Predefined requirement specifications are required to generate a basic design. The workflow parses these requirements to automate initial drafts, validate the technical stack, and run iterative quality assurance loops, ensuring the output meets architectural standards.

What is the best way to ensure technical completeness before detailed software design?

Ensuring technical completeness before detailed software design involves running an iterative quality assurance loop on the basic design draft. This process validates the technical stack and refines the document until it meets a minimum 9-point score for architectural adherence.