Loading...
Loading...
Found 12 Skills
CEO/Founder-mode plan review. Rethink the problem, find the 10-star product, challenge premises, expand scope when it creates a better product. Four modes: SCOPE EXPANSION (dream big), SELECTIVE EXPANSION (hold scope + cherry-pick), HOLD SCOPE (maximum rigor), SCOPE REDUCTION (strip to essentials). Adapted from gstack/plan-ceo-review (Garry Tan, MIT license).
Generate technical plan, data model, and interface contracts from spec.md
Turn ambiguous coding requests into verified Cursor Agent implementation specs. Use when the user wants requirements, an implementation plan, or a spec before coding; include source checks, needed ADRs, and agreed delivery. Do not use for already specified direct implementation or memory cleanup.
Create UX-first plans as flow trees, then attach concrete function names, files, and implementation anchors after the high-level flow is clear.
[BETA] Stress-test an existing implementation plan and selectively strengthen weak sections with targeted research. Use when a plan needs more confidence around decisions, sequencing, system-wide impact, risks, or verification. Best for Standard or Deep plans, or high-risk topics such as auth, payments, migrations, external APIs, and security. For structural or clarity improvements, prefer document-review instead.
Resolve ambiguities in spec.md through targeted Q&A before planning
Stress-test a plan by walking its decision tree one question at a time. Use when the user wants to pressure-test a design before implementation.
Implementation planning skill. Creates detailed technical plans through interactive research and iteration.
Evaluate whether a software idea is worth building, then write the proposal document. Use when the user wants to assess an idea, says "evaluate", "propose", "is this worth building", or "should we build". If the idea passes evaluation, write the proposal document using the provided template.
Use when the user wants to turn agreed ideas, decisions, a plan, or prototype findings into an implementation brief or dependency-aware delivery tickets.
Design a software change and break it into implementable tasks. Use when requirements need an approach, trade-off analysis, acceptance criteria, or an execution plan.
Select relevant design lenses for a planned slice and return a proceed-or-revise verdict. Use during task planning or when a design boundary changes; invoke a named lens directly for a single-lens review.