Does this skill modify my source code?

No, the Decision Checklist skill is designed to perform evaluations and provide feedback only; it does not edit, add, or delete files.

Can I use this for API design?

Yes, it specifically validates whether designs prioritize contracts as the source of truth and maintains clear boundaries between backend services.

How does it help with long-term maintenance?

It proactively checks for future-proofing factors like extensibility and ensures that implementation costs align with the projected value of the feature.

When is the best time to run this skill?

It is best utilized during the planning or design phase, immediately before finalizing a technical decision or starting a major implementation.

What specific domains is this checklist optimized for?

While broadly applicable to software engineering, it includes specific considerations for Discord bot development (TTS/settings) and API-bot responsibility separation.

Decision Design Checklist

Name: Decision Design Checklist
Author: Hakuya5247

byHakuya5247

Productivity & Workflow

Validates architectural and design decisions against a standardized checklist to ensure maintainability and scalability.

About

The Decision Design Checklist skill acts as a critical quality gate for developers using Claude Code, ensuring that architectural choices are sound before any code is committed. It systematically evaluates proposed changes for breaking impacts, future-proofing (specifically for TTS and settings), contract adherence, and clear separation of concerns between bot and API layers. By assessing the balance between implementation cost and value, it helps maintain long-term project health without modifying any source files directly.

Key Features

Bot and API responsibility separation check
0 GitHub stars
Breaking change impact analysis
Contract-first design validation
Cost-benefit value assessment
Extensibility verification for TTS and settings

Use Cases

Ensuring strict adherence to predefined API contracts during the design phase.
Refactoring validation to ensure future extensibility isn't compromised by immediate changes.
Pre-implementation architectural review for Discord bots or similar modular systems.

About

Key Features

Bot and API responsibility separation check
0 GitHub stars
Breaking change impact analysis
Contract-first design validation
Cost-benefit value assessment
Extensibility verification for TTS and settings

Use Cases

Ensuring strict adherence to predefined API contracts during the design phase.
Refactoring validation to ensure future extensibility isn't compromised by immediate changes.
Pre-implementation architectural review for Discord bots or similar modular systems.