agentsclimarketplace
Sign in

Design exploration

Skill jagreehal/jagreehal-claude-skills/skills/design-exploration

Explores intent, requirements, and trade-offs through dialogue before code, producing a validated design document. Use this skill when requirements are ambiguous before features, components, or significant behavior changes. Do not use when/for bite-sized coding plans after design is approved (use implementation-planning) or debugging an existing failure.From its SKILL.md

Install
npx -y skills add jagreehal/jagreehal-claude-skills --skill design-exploration

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.1 KB, as published. Nobody here has run it

Design Exploration

Critical rules

  • NO IMPLEMENTATION WITHOUT DESIGN AGREEMENT FIRST. No production code until the human validates the design.
  • One question per message; prefer multiple choice when options are known.
  • Present 2-3 approaches with trade-offs and a recommendation — never only one option.
  • YAGNI ruthlessly. Never silently fill ambiguous requirements.
  • Present design in 200-300 word sections; confirm each before continuing.
  • Before questioning patterns or writing the doc, read references/process-and-template.md.

Workflow

  1. Understand context: project state, related code, existing patterns.
  2. Clarify intent: purpose, constraints, success criteria — one question at a time.
  3. Explore 2-3 approaches with explicit trade-offs; lead with recommendation.
  4. Present design in sections (architecture, components, data flow, errors, testing); confirm each.
  5. Write validated design to docs/plans/YYYY-MM-DD-<topic>-design.md, commit, ask ready for implementation (implementation-planning / git-worktrees).

Resources

Validation

  • Existing state and patterns understood
  • Ambiguities clarified one question at a time
  • 2-3 approaches with trade-offs and recommendation
  • Design covers architecture, components, data flow, errors, testing
  • Human approved each section; doc saved and committed

Constraints

  • Skip for unambiguous single-file changes, typos, or already-approved designs.
  • Related: implementation-planning, git-worktrees, tdd-workflow.

Keep looking

Skills are one crate of 627,801. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.