skills.rest
isizono
isizonoCOMMUNITY
Explore all skills by this author →
GitHub

design

Document implementation decisions for How, Interface, Edge cases, and Verification.

1|Updated Dec 9, 2025
Search Tags:#design#architecture#requirements#verification#edge-cases#decision-making#non-functional
One-click install
npx skills add https://github.com/isizono/claude-code-exterminal-memory --skill design-isizono
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: design
Source: https://github.com/isizono/claude-code-exterminal-memory/tree/main/.claude/skills/design
Command: npx skills add https://github.com/isizono/claude-code-exterminal-memory --skill design-isizono

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill determines implementation approach and technical decisions. Use when How/Interface/Edge cases need decisions, or when working on a cc-memory task with [設計] prefix.

Core Features & Use Cases

  • Clarifies What/Why/Scope/Acceptance from existing discussions and translates them into How/Interface/Edge cases/Verification requirements for the design phase.
  • Creates or extends [設計] tasks to capture concrete design decisions and implementation plans.
  • Coordinates with 議論フェーズ and ensures guardrails for edge cases and verification before implementation.

Quick Start

Identify a related [議論] task, confirm What/Why/Scope/Acceptance, and if no [設計] task exists, create one to begin design.

Frequently Asked Questions about design

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

FAQPage Schema
How do I document software design decisions for implementation?▼

To document software design decisions, you capture and organize implementation approaches by explicitly recording How, Interface, Edge cases, Verification, and Non-functional considerations as structured design decisions.

What is the best way to translate requirements into design phase specifications?▼

Translating requirements into design specifications involves clarifying What, Why, Scope, and Acceptance from discussions, then converting them into concrete How, Interface, and Verification requirements.

How do I handle edge cases and verification before starting implementation?▼

Handling edge cases and verification requires establishing guardrails during the design phase by explicitly documenting edge case scenarios and verification requirements as part of your design decisions.

When do I need to create a design task for software architecture decisions?▼

You need to create a design task when decisions about How, Interface, Edge cases, and Verification are required, or when working on tasks with a design prefix in a cc-memory project.

Can I use this approach for non-functional requirements in software architecture?▼

Yes, this approach supports non-functional requirements by requiring you to document non-functional considerations as explicit design decisions alongside implementation and interface choices.

Related Skills

Explore More Software Engineering Skills→
isizonoisizono
1

discussion

Clarify user requirements and record decisions using What/Why/Scope/Acceptance.

Community
Intermediate
Jesse-L-MJesse-L-M

plan-design-review

Identify missing design decisions in UI plans before implementation.

Community
Advanced
patrickrmoorepatrickrmoore

sddp-tasks

Decompose feature implementation plans into phase-organized developer tasks.

Community
Advanced
dralgorhythmdralgorhythm
111

requirements-analysis

Clarify ambiguous product requirements using Five Whys, SMART, and edge-case analysis.

Community
Intermediate