Score concepts on impact/delight/effort and pick a 1-day spike.
The concept-forge skill helps teams decide which idea to test first when they already have several potential concepts. It provides a structured way to evaluate and prioritize ideas using clear scoring criteria, ensuring decisions are grounded in impact, delight, and effort. This skill is designed to reduce ambiguity in early-stage decision-making by transforming loosely defined ideas into comparable concept cards and selecting a focused 1-day spike to validate the most promising direction.
Its core capabilities include capturing the problem statement, defining success signals, and documenting constraints before evaluation begins. It then generates 4–6 concept cards, each scored on Impact (1–5), Delight (1–5), and Effort (S/M/L), and annotated with risks and a proposed 1-day spike. Concepts are ranked by a chosen scoring axis, with lowest effort used as a tie-breaker. The skill concludes by recommending the top concept and its associated spike, outlining verification steps, and optionally seeding follow-up tasks or handing off to a planning workflow for execution.
This skill is well-suited for product teams, innovation groups, and collaborative workshops where multiple ideas compete for limited time or resources. It is particularly useful after idea-generation sessions and before execution planning. Teams seeking a fast, disciplined way to move from brainstorming to validated experimentation can use concept-forge to align on priorities and take immediate, testable action.
Use it after generating several ideas and when you need to decide which one to test first. It is intended for prioritizing concepts before committing execution resources.
You need a clear problem statement, a chosen scoring axis (impact, delight, or effort), and any constraints that must be honored.
Concepts are ranked by the selected scoring axis. If two concepts tie, the one with the lower effort is prioritized.
Yes. It can follow idea-generation workflows to evaluate options and can hand off to a planning workflow for execution. It can also be paired with a pre-mortem process to assess risks.
No. It recommends a 1-day spike and provides verification steps, but execution is handled separately or through a follow-up planning workflow.
Quick Setup:
.claude/skills/Repository
NickCrew/claude-cortex