discuss-design

Files (2)

• SKILL.md
• metadata.yml

SKILL.md (first lines)

# Discuss Design

Interview the user about all aspects of this plan until we have reached a shared understanding on all of the main technical decisions.

The goal is to ensure that you are fully aligned with the user on the direction to take before doing any implementation.

## Workflow

1. Make sure you are in sync with the user about the overall goal or problem and its context and constraints. Ask for clarity if needed.
2. Repeat the following steps as many times as necessary, until all design decisions are resolved:
    1. Examine the current context and plan for lingering assumptions or questions or areas where you may have to jump to conclusions.
    2. Laser in on _one_ particular question.
       - Ask questions one at a time to maintain a steady conversational pace.
    3. Explore the codebase to see if the question can be answered by existing code.
       - If `yes`, update the current context/plan with the answer and go back to step 1.
       - If `no`, proceed to step 4.
    4. Present a couple sentences explaining why the question needs answered.
    5. Come up with 3-4 possible answers and present them to the user.
       - Highlight which one is your recommended solution.
       - Include one pro and one con for each alternative.
       - Add one option for "Explain in more detail, then ask again".
3. At the end of the discussion, give a brief summary of each decision that was made.

## Guidelines

- **Always** walk down all branches of the design tree, resolving each decision one-by-one. Stay focused on the task at hand.
  - **Never** make premature conclusions or rush ahead.
- **Always** focus on design concepts. **Ask approval** before getting into nitty-gritty implementation details, and avoid doing so if possible, because it bogs down a discussion very quickly.
- **Never** implement anything unless explicitly told to do so.

## Output

Summary of the discussion's decisions in bullet points.

## Gotchas

- Do not dig too deep into little implementation details during the discussion.

From bambam955/skills, MIT.

More from bambam955/skills