starting-a-design-plan

Orchestrate a six-phase design process with automated documentation and planning handoff.

8|1|Updated Feb 25, 2022
One-click install
npx skills add https://github.com/ayubun/dotfiles --skill starting-a-design-plan-ayubun
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: starting-a-design-plan
Source: https://github.com/ayubun/dotfiles/tree/main/configs/opencode/skills/ed3d-plan-and-execute/starting-a-design-plan
Command: npx skills add https://github.com/ayubun/dotfiles --skill starting-a-design-plan-ayubun

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill addresses the challenge of initiating and guiding a comprehensive design process, ensuring clarity, collaboration, and documentation from concept to implementation-ready plans.

Core Features & Use Cases

  • Structured Workflow: Facilitates a six-phase design process for clarity and consistency.
  • Collaborative Validation: Involves users in refining requirements and validating design.
  • Documentation Automation: Generates and updates design documents throughout the process.
  • Use Case: Ideal for project managers and designers who need a systematic approach to create detailed design plans for software, product, or service development.

Quick Start

Use the starting-a-design-plan skill to initiate a new design project by running the command: /starting-a-design-plan

Frequently Asked Questions about starting-a-design-plan

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

FAQPage Schema
How do I structure a design process from concept to implementation-ready plans?

Structure a design process through six phases: context gathering, clarification, definition of done, brainstorming, design documentation, and planning handoff. This workflow ensures collaboration, validates requirements, and automates documentation for implementation-ready plans.

What is the best way to document design requirements collaboratively?

Document design requirements collaboratively by involving users in refining requirements and validating design across structured phases. This approach ensures clarity from concept to implementation and automatically generates and updates design documents throughout the process.

Can I use this structured design workflow for software and product development?

Yes, you can use this structured design workflow for software, product, or service development. It is ideal for project managers and designers who need a systematic approach to create detailed design plans and handle project-specific guidance.

How do I define the "definition of done" for a design project?

Define the "definition of done" during a dedicated phase within the structured design workflow. This phase follows context gathering and clarification, ensuring all collaborators understand project-specific guidance and validation criteria before brainstorming begins.

What is included in a planning handoff for design documentation?

A planning handoff for design documentation includes the finalized design plans generated through the structured workflow. It represents the final phase, delivering implementation-ready plans with automated documentation and validated requirements to development teams.

When do I need a structured workflow for design documentation?

You need a structured workflow for design documentation when initiating a comprehensive design process that requires clarity, collaboration, and validation from concept to implementation-ready plans. It prevents misalignment by automating documentation across six distinct phases.