design

Facilitate collaborative software design discussions and generate formal design documents.

30|1|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/pacaplan/flokay --skill design-pacaplan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design
Source: https://github.com/pacaplan/flokay/tree/main/skills/design
Command: npx skills add https://github.com/pacaplan/flokay --skill design-pacaplan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps users transform initial ideas into well-defined software designs through a structured, collaborative brainstorming process, ensuring clarity and alignment before implementation.

Core Features & Use Cases

  • Idea Refinement: Guides users through clarifying questions to understand project context, purpose, and constraints.
  • Approach Exploration: Proposes and discusses 2-3 alternative design approaches with their respective trade-offs.
  • Design Documentation: Generates a formal design document based on the approved design.
  • Use Case: When starting a new feature, use this Skill to brainstorm different architectural patterns, discuss potential challenges, and arrive at a consensus on the best approach before writing any code.

Quick Start

Use the design skill to create a design for the new user authentication module.

Frequently Asked Questions about design

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

FAQPage Schema
How do I brainstorm and document software architecture before starting development?

To brainstorm software architecture, you can collaboratively refine initial ideas, explore 2-3 alternative design approaches with trade-offs, and generate a formal design document. This structured process ensures technical direction and project scope are clearly defined before implementation begins.

What is the best way to explore architectural trade-offs for a new feature?

The best way to explore architectural trade-offs is through a guided collaborative dialogue that proposes multiple design approaches. By discussing the respective advantages and constraints of each pattern, you can arrive at a consensus on the optimal technical direction.

How do I create a formal design document from initial project ideas?

You create a formal design document by iteratively discussing project context and constraints, selecting an approved design approach, and finalizing the details. The process requires user feedback and approval to ensure the software design artifacts accurately reflect the intended scope.

Can I use collaborative brainstorming to define technical direction for my software project?

Yes, you can use collaborative brainstorming to define technical direction by working through clarifying questions about your project purpose. This interactive process helps transform initial ideas into well-defined software designs, ensuring alignment before any code is written.

Does the software design process require my approval before finalizing documentation?

Yes, the software design process explicitly requires iterative user feedback and approval before finalizing design documents. This ensures the chosen architecture and project scope accurately match your expectations and constraints before development starts.