Works with the AI tools you already use
Claude Code
Cursor
Codex CLI
Muse
Dots+22 moreClaude CodeCursorCodex CLIMuseDots
OpenClaw
Manus
Grok
Grok Bot+18 agentsConcept Exploration & Design Gate
Turns every request into an approved, documented design before a line of code is written, eliminating rework caused by hidden assumptions and scope drift.
Free
Concept Exploration & Design Gate
Example session with this skill installed
I want to add a bulk invoice export feature to our billing app (Rails 7, Postgres, in /home/me/billing). Customers keep asking to download invoices as PDF and CSV, and I imagine an Export button on the invoices page. The repo has a README, some half-finished reports code, and recent commits around payment webhooks. Before anyone writes code, run the full concept exploration on this: inspect the project context, interview me one question at a time about what actually matters, compare the realistic approaches with trade-offs and a recommendation, get my sign-off section by section, write the final design doc under docs/designs/, and then move into implementation planning.
- Read your context and instructions
- Compiled the concept exploration
- Generated the UI component
Summary
Concept exploration for the bulk invoice export feature is complete. Requirements were locked through six sequential questions, three approaches were compared, and the approved design is committed to docs/designs/2026-09-14-invoice-export.md. No code was written — implementation is ready to plan.
| Item | Before | After |
|---|---|---|
| Scope | 'add PDF export' | CSV + PDF, up to 10k rows, async job |
| Open questions | 7 unresolved | 0 — all answered |
| Approaches | none | 3 compared, 1 recommended |
| Design record | none | docs/designs/2026-09-14-invoice-export.md (commit a41f9c2) |
Key decisions
- Async background job chosen over synchronous download: p95 for 10k rows exceeds request timeout
- Reuses the existing ReportService queue instead of introducing Celery
- YAGNI: email-delivery option dropped; users download from the UI
Next steps
- Invoke writing-plans to convert the approved design into a phased roadmap
- Review the committed design doc before the plan starts
- Revisit success criteria (export under 45s per 1k rows) at acceptance testing
concept-exploration-design-gate.tsx
TSX · React component
Example file from a real run - the skill writes it into your workspace.
Connects securely to your tools. The creator never sees your data.
About this skill
Stop wasting hours on rework caused by misunderstood requirements and scope drift. This skill enforces a design-first workflow, ensuring every feature, refactor, or component is fully architected and approved before a single line of code is written. It transforms vague requests into structured technical documentation through systematic inquiry.
What it does
- Intent clarification by asking sequential, focused questions to uncover hidden constraints and success criteria.
- Approach exploration by generating 2-3 distinct solution paths with analyzed trade-offs and expert recommendations.
- Incremental validation through section-by-section design presentations that require explicit user sign-off.
- Automated documentation by generating and committing design specs to
docs/designs/for permanent record. - Implementation handoff by preparing the context needed to transition directly into detailed planning skills.
How it works
- Context discovery scans your current codebase and recent commits to understand the existing state.
- Clarification loops use structured, often multiple-choice questions to define the "why" and "what" without ambiguity.
- Design drafting presents the architecture, data flow, and error handling for your review.
- Final approval triggers the creation of a dated design markdown file and its commit to your repository.
Frameworks & tools
This skill is platform-agnostic and works with any tech stack. It utilizes Mermaid.js for flowcharts and follows YAGNI principles to ensure lean architecture.
Why this beats prompting it yourself
Generic prompts often jump straight to code, missing edge cases and integration impacts. This skill enforces a strict gate, preventing the AI from "hallucinating" an implementation plan before you have agreed on the fundamental architecture.
Use cases
- Defining the architecture for a new microservice or API endpoint.
- Mapping out complex state management changes in a frontend application.
- Evaluating trade-offs between different third-party library integrations.
- Establishing a shared source of truth for a feature before team execution.
Known limitations
Does not perform the actual coding or implementation; it is strictly a design and alignment gate. Requires the writing-plans skill for the subsequent implementation roadmap.
How to install
Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.
- 1
Download the ZIP
Free skills download straight away. Paid skills unlock right after purchase.
- 2
Unzip into your skills folder
Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.
- 3
Ask your agent to use it
Restart the agent if it was already running. It picks the skill up automatically - no config needed.
Skills folder by agent
Click the path to copy it. Create the folder if it does not exist yet.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill passes our trust checks below.
Security scanned
Passed our 8-point scan before listing
Fresh listing
Recently published to Agensi
Free forever
No account required to browse
Trust & safety
Security scanned
Verified clean today
- Free to download with an account