design-first

Convert feature requests into approved implementation designs before coding.

13|5|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/Jonghakseo/my-pi --skill design-first-jonghakseo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-first
Source: https://github.com/Jonghakseo/my-pi/tree/main/skills/design-first
Command: npx skills add https://github.com/Jonghakseo/my-pi --skill design-first-jonghakseo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents premature implementation, unclear requirements, and costly rework by requiring an approved design before code is written.

Core Features & Use Cases

  • Context and Impact Analysis: Reviews the codebase, documentation, dependencies, callers, test coverage, and change blast radius before proposing a solution.
  • Structured Design Process: Asks focused clarification questions, compares two or three approaches, verifies external documentation, and presents the design incrementally for approval.
  • Execution Handoff: Converts the approved design into bite-sized implementation tasks with exact files, tests, commands, expected results, and an optional worker-verifier-reviewer pipeline.
  • Use Case: Use it before adding a major feature or changing a shared module to identify risks, eliminate unnecessary scope, and obtain explicit approval for an actionable implementation plan.

Quick Start

Use the design-first skill to analyze the requested change, propose alternatives, obtain approval, and produce a testable implementation plan before writing code.

Frequently Asked Questions about design-first

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

FAQPage Schema
How do I plan architecture and evaluate impact before writing code?

Implementation planning requires converting feature requests into an approved design by inspecting the repository, scoring change blast radius, and verifying external documentation before any code is written.

What is the best way to analyze blast radius for a shared module modification?

Blast radius analysis reviews codebase dependencies, callers, and test coverage to identify risks and eliminate unnecessary scope before proposing an architectural change.

How do I clarify requirements and compare alternatives for a new software feature?

Requirements clarification involves asking focused questions and comparing two or three architectural approaches to verify external documentation and present the design incrementally for stakeholder approval.

Does this design-first approach work for incremental architecture approval?

Yes, the design process presents architectural changes incrementally for explicit approval, then converts the approved design into bite-sized implementation tasks with exact files, tests, and expected results.

When should I not use a design approval process for software development?

You should bypass design approval for trivial modifications or isolated bug fixes where impact analysis is unnecessary, reserving this structured process for major features and shared-module changes requiring stakeholder approval.