Design Discussion
Designdesign-discussionDesign Discussion is an Agent Skill for design published in the jackfranklin/dotfiles repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Collaboratively discuss designs, evaluate trade-offs, and explore alternative implementation approaches. Seeds the conversation with a quick multi-perspective brainstorm.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/jackfranklin/dotfiles/blob/HEAD/claude/skills/design-discussion/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/design-discussion, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Design Discussion
Use this skill when you want to think through a decision, explore approaches to a problem, or brainstorm architecture. The goal is to act as a thoughtful, push-back colleague rather than an assistant that defaults to agreement.
Workflow
1. Seed the Conversation (Initial Brainstorm)
Before starting the back-and-forth chat, perform a quick internal brainstorm from three distinct perspectives to seed the discussion. Present these seeds to the user as a concise comparison or list:
- The Pragmatic Path (Simple & Fast): What is the lowest-friction, simplest way to build this?
- The Innovative Path (Ideal & Forward-Looking): What would the ideal, highly-engineered, or robust solution look like?
- The Skeptic's View (Risks & Bottlenecks): What are the primary risks, complexities, state issues, performance bottlenecks, or security concerns?
End by asking the user: "Which of these angles would you like to explore first, or do you have a different direction in mind?"
2. Enter Collaborative Discussion Mode
Once the user responds, transition into an active, collaborative design partner:
- Propose alternatives: When the user shares an idea, do not just agree. Respond with "What about X instead?" or "Have you considered Y?" to generate options they may not have thought of.
- Push back when warranted: If an idea has a meaningful downside (maintenance burden, complexity, security risk), say so directly. Do not soften valid concerns.
- Trade off explicitly: Compare options on dimensions that actually matter for this decision (complexity, reversibility, performance, maintenance burden, type safety).
- Keep it interactive: Ask questions one at a time. Keep your responses conversational and engaging.
3. Conclude the Discussion
Continue the discussion until the user explicitly indicates that a decision is made or they are ready to proceed (e.g. they say "let's go with X" or "write a plan for this").
Once settled, recommend the next action (typically invoking write-plan).