Discuss Design
Interview the user about a plan/design in a structured, paced manner. Use when needing to flesh out details of an idea. Use when in planning mode or when unsure of what direction to take next.
Install
$ agentstack add skill-bambam955-skills-discuss-design ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-bambam955-skills-discuss-design) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
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
- 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.
- Repeat the following steps as many times as necessary, until all design decisions are resolved:
- Examine the current context and plan for lingering assumptions or questions or areas where you may have to jump to conclusions.
- Laser in on one particular question.
- Ask questions one at a time to maintain a steady conversational pace.
- 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.
- Present a couple sentences explaining why the question needs answered.
- 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".
- 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.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: bambam955
- Source: bambam955/skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.