discovery
From the author
Structured pre-design questioning to surface hidden constraints before any architecture decision is locked in. Forces the architect/auditor/reviewer to enumerate what they DON'T know before proposing.
Install
npx skills add avelikiy/great_cto --skill discovery -a claude-code
Installs to .claude/skills/discovery/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 83
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- solution-designthiientv/godmodeExplores ambiguous product or engineering intent before implementation, clarifies users, constraints, alternatives, risks, and acceptance criteria, and turns the result into an approved design direction. Use for a new feature, subsystem, creative UI, architecture change, or unclear request. Not for an already-scoped bug fix, an existing implementation plan, or a narrow code review.Design★ 99
- solution-explorationcbrock84/headcountExplores the problem and the range of possible approaches before any code is written — clarifying what is actually being asked, surfacing options with their tradeoffs, and converging on one. Use this at the start of any feature, component, or behavior change, when a request is ambiguous, when the first idea is the only idea on the table, or when a design decision needs pressure-testing before commitment.Testing★ 2.1K
- designhashgraph-online/awesome-codex-pluginsUse for standard or complex new work before coding or planning. Also handles vague goals — clarifies before designing.Design★ 1.4K
- vibe-research-before-designash1794/vibe-engineeringResearches real projects, papers, and documented failures before proposing a new feature, architecture, or technology choice. Use for design decisions with multiple valid approaches, not for implementing an existing spec or fixing a known bug.Design★ 165
- solution-architecturecbrock84/headcountDesigns system structure and makes architectural decisions defensible — boundaries, coupling, trade-offs, and recording why. Use this to design a new system or major component, choose between architectural options, review an existing design, decide where a boundary belongs, or document an architectural decision so it survives the people who made it.Planning★ 2.1K
- architecture-aware-initathola/claude-night-marketSelects architecture paradigm via research before scaffolding. Use when architecture is undecided and the choice needs justification and documentation.Planning★ 343
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in