starting-a-design-plan

Orchestrate six design phases from context gathering to planning handoff.

5|1|Updated Jan 26, 2026
One-click install
npx skills add https://github.com/ed3dai/ed3d-plugins-testing --skill starting-a-design-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: starting-a-design-plan
Source: https://github.com/ed3dai/ed3d-plugins-testing/tree/main/plugins/ed3d-plan-and-execute/skills/starting-a-design-plan
Command: npx skills add https://github.com/ed3dai/ed3d-plugins-testing --skill starting-a-design-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill orchestrates the entire design workflow, guiding teams from initial idea to implementation-ready documentation.

Core Features & Use Cases

  • Orchestrates six design phases: context gathering, clarification, definition of done, brainstorming, design documentation, and planning handoff.
  • Ensures a clear Definition of Done before brainstorming and provides a structured design document for implementation planning.
  • Supports repeatable workflows for new features, research projects, or product initiatives, improving alignment and reducing design drift.

Quick Start

Start the design process by invoking this skill at the beginning of a project, providing goals, constraints, and any relevant context. The skill will collect input, ask clarifying questions if needed, and generate a design document outline and handoff 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 create a structured design plan for a new feature launch?

To create a structured design plan, orchestrate the design workflow from context gathering to design handoff to produce an implementation-ready document. This ensures alignment and validates the definition of done before work begins.

What is a design document and when do I need one for project management?

A design document is an implementation-ready output generated during the design process. You need one at the start of any design effort, including feature launches or research projects, to ensure alignment and reduce design drift.

Can I use this design process for cross-functional initiatives without external tooling?

Yes, you can use this design process for cross-functional initiatives without external tooling. It relies entirely on internal orchestration and sub-skills for clarification and brainstorming to deliver a concrete plan.

What's the best way to define requirements gathering before brainstorming a design?

The best way to define requirements gathering before brainstorming is to establish a clear definition of done during the clarification phase. This ensures structured alignment and validated goals before design documentation begins.

How does design handoff work after finalizing the design document?

Design handoff works by producing a structured design document and planning handoff at the end of the workflow. This final phase delivers implementation-ready documentation for downstream planning.