What happens after the design phase is complete?

The skill generates a structured Markdown document for version control and provides a workflow to transition into implementation using task-planning skills.

How does the 'One Question at a Time' rule help?

It prevents cognitive overload for the user, allows for deeper reflection on specific design points, and ensures the AI builds a more accurate mental model of the project goals.

When should I use the Methodology skill?

Use it during the initial creative development phase for new features, complex architecture decisions, or when requirements are still unclear and need refining.

Can I use this for simple bug fixes?

It is generally not recommended for mechanical processes or simple bug fixes with obvious solutions; it is specifically designed for tasks where multiple valid approaches exist.

Interactive Design Methodology

Name: Interactive Design Methodology
Author: duthaho

byduthaho

•

Productivity & Workflow

Refines rough ideas into production-ready designs through structured, interactive dialogue and comparative trade-off analysis.

About

The Methodology skill facilitates a collaborative three-phase process—Understanding, Exploration, and Design Presentation—to help developers transform ambiguous requirements into solid architectural plans. By enforcing sequential questioning and 'ruthless YAGNI' principles, it ensures that designs are lean, validated, and documented before implementation begins. It is particularly effective for navigating complex architectural decisions, refining feature requirements, and leveraging MCP tools like Sequential Thinking to build a persistent, reasoned design history.

Key Features

MCP integration for persistent memory and data-grounded technology choices
Comparative approach analysis with structured pros/cons and trade-off summaries
Ruthless YAGNI-based feature pruning to focus on minimum viable designs
27 GitHub stars
Sequential questioning to prevent information overload during requirements gathering
Automated generation of timestamped Markdown design documents

Use Cases

Architecting new features with complex or ambiguous requirements
Evaluating trade-offs between different technical implementation approaches
Breaking down complex problems into digestible design components and data flows

About

Key Features

MCP integration for persistent memory and data-grounded technology choices
Comparative approach analysis with structured pros/cons and trade-off summaries
Ruthless YAGNI-based feature pruning to focus on minimum viable designs
27 GitHub stars
Sequential questioning to prevent information overload during requirements gathering
Automated generation of timestamped Markdown design documents

Use Cases

Architecting new features with complex or ambiguous requirements
Evaluating trade-offs between different technical implementation approaches
Breaking down complex problems into digestible design components and data flows