skills.rest
drimchansky
drimchanskyCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

design

Plan software features by decomposing tasks, comparing approaches, and identifying risks.

Updated Feb 8, 2026
Search Tags:#design#planning#architecture#scoping#task breakdown#risk assessment
One-click install
npx skills add https://github.com/drimchansky/agents-kit --skill design-drimchansky
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: design
Source: https://github.com/drimchansky/agents-kit/tree/main/skills/design
Command: npx skills add https://github.com/drimchansky/agents-kit --skill design-drimchansky

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured approach to planning and designing software features, ensuring clarity, identifying risks, and defining scope before implementation begins.

Core Features & Use Cases

  • Task Decomposition: Breaks down complex tasks into manageable, verifiable steps.
  • Approach Comparison: Evaluates multiple implementation strategies, highlighting trade-offs.
  • Risk Identification: Surfaces potential issues and suggests mitigation strategies.
  • Scope Definition: Clearly delineates what is included and excluded from the task.
  • Use Case: Before starting a major refactor of a core service, use this skill to create a detailed plan, compare different architectural approaches, and identify potential impacts on other parts of the system.

Quick Start

Use the design skill to create a detailed implementation plan 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 break down complex software features into actionable steps?▼

Task decomposition breaks complex software features into manageable, verifiable steps. This approach ensures clarity by defining scope and identifying potential risks before implementation begins.

What is the best way to compare implementation approaches for a major refactor?▼

Approach comparison evaluates multiple implementation strategies for a major refactor by highlighting trade-offs. This structured analysis identifies potential risks and suggests mitigation strategies for cross-cutting changes.

Do I need formal scope definition before starting cross-cutting architectural changes?▼

Formal scope definition is required before starting cross-cutting architectural changes. It provides a structured approach to planning, ensuring clarity and identifying risks for complex, multi-file modifications.

When should I use architectural planning for software features instead of direct implementation?▼

Architectural planning should be used instead of direct implementation when facing complex, multi-file, or cross-cutting changes. It facilitates task decomposition and approach comparison to prevent risks before coding starts.

Can I use task breakdown to identify risks in a new user authentication module?▼

Task breakdown identifies risks in a new user authentication module by decomposing the work into verifiable steps. It evaluates implementation approaches and defines clear scope boundaries for the feature.

Related Skills

Explore More Software Engineering Skills→
OzeroHAXOzeroHAX
32

docs-project-brief

Define project context, problem statement, and MVP boundaries.

Community
Basic
abcnutsabcnuts
60

executing-plans

Execute implementation plans in batches with review gates and safety checks.

Community
Advanced
rozxrozx
25

openspec-verify-change

Verify code changes against specs, tasks, and design artifacts.

Community
Advanced
dralgorhythmdralgorhythm
111

agile-methodology

Automate agile ceremonies and backlog management for Scrum and Kanban teams.

Community
Intermediate