leszekgruchala/buddy / skills/innovate
innovate
VerifiedExplore requested solution alternatives and trade-offs before spec without choosing or implementing one; prior research is optional. Keep the current request in this skill; route new requests by their own scope.
Innovate
Keep the current request in this skill. Do not activate another Buddy skill without user or develop direction. Workers return to their caller. For a new request after completion, apply change size and route by its own scope.
Produce options only. Do not decide, specify, or implement.
Model selection
Apply model selection; recommend balanced.
Rules
- Read the exact passed context/artifact, never an input selected by recency.
- Start from the problem and its success conditions, not from the first idea. An approach the request names is one candidate, not the answer.
- Start from the solution-space facts in passed research and search again only for gaps. Widen before narrowing: consider reuse, another layer, an established pattern or library, and no code change.
- Present the best two or three viable options from safest to boldest, each with value, cost, risk, fit, and the condition that would make it fail. Options differ in mechanism, not in detail; never add a weak option to fill a slot. Present one only when evidence rules out the others, and state how.
- Verify in code or primary documentation only the option-deciding facts that the artifact does not already establish; label what stays unverified.
- Keep implementation detail for
spec. - Return options and a recommendation: the option that best meets the success conditions on the evidence, the simplest when options tie. Name the fact that would change it. Only the user or
develop, through its judge, chooses the direction and next stage.
When a research artifact is passed, add or update its ## INNOVATION section before REJECTED; otherwise create no artifact. Follow the artifact update and length rules in research. Keep only options still under consideration; move each option that the user, develop, its judge, or evidence rules out to REJECTED as one line with its reason, and delete superseded options.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |