Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
What This Skill Does
A structured pre-coding workflow that uses Socratic questioning to clarify vague feature requests. The agent asks about goals, constraints, and success criteria, then presents 2-3 implementation approaches with trade-offs before writing any code. It produces a design document saved to the project repo.
Forces requirement gaps to surface before implementation begins, avoiding the cost of rewriting code that solved the wrong problem.
When to use it
- Clarifying a vague 'make it better' request before touching code
- Choosing between a quick fix and a more robust architecture
- Documenting design decisions before a large refactor
- Aligning on success criteria when a feature affects multiple components
- Capturing edge cases before writing tests
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: Add caching to the app
- 1Asks what should be cached, what the invalidation strategy is, and what staleness is acceptable
- 2Presents three approaches: in-memory cache, Redis with TTL, and event-based invalidation with trade-offs and complexity scores for each
- 3User selects Redis with TTL; agent drafts a design document covering problem statement, solution, affected components, edge cases, and success criteria
- 4Saves design doc to docs/design/2026-03-16-add-caching.md
- 5Passes design doc to the writing-plans skill for implementation planning
Design document saved to docs/design/2026-03-16-add-caching.md, ready for planning phase