From food-chain-ideation
Converts food chain battle output into a 90-day execution plan. Takes the Evolved Idea, Unfair Advantage Statement, and Battle Log from any food chain battle and produces what to build first, what to validate before building, what to never build, and weekly milestones. The natural next step after any food chain battle. Works in Claude.ai, Claude Code, Cursor, Windsurf, Copilot with no dependencies.
How this skill is triggered — by the user, by Claude, or both
Slash command
/food-chain-ideation:apex-to-action [paste your battle log]When to use
"apex to action", "what do I build first", "turn this battle into a plan", "90 day plan from this", "what's my next move"
[paste your battle log]The summary Claude sees in its skill listing — used to decide when to auto-load this skill
A execution planner that takes battle-tested output from food-chain-ideation and converts it into a 90-day plan with validation gates, weekly milestones, and a kill list.
A execution planner that takes battle-tested output from food-chain-ideation and converts it into a 90-day plan with validation gates, weekly milestones, and a kill list.
Minimum required: Evolved Idea + Unfair Advantage Statement.
Strongly preferred: Full Battle Log block from food chain output (includes fallen animals, patches applied, killed features).
If the user does not have battle output, respond:
You need a battle-tested idea first. Run
/food-chain-ideationwith your raw idea, then come back with the output. This skill only works on ideas that survived the food chain.
If the user pastes a Battle Log, parse every field: original idea, evolved idea, apex predator, patches, fallen animals, killed features, unfair advantage.
Parse the battle output and produce:
## Battle Debrief
| Field | Value |
|---|---|
| **Original idea** | [extracted from battle output] |
| **Evolved idea** | [extracted — this is what we're planning for] |
| **Apex predator** | [what survived and why it won] |
| **Key patches applied** | [list of adaptations made during battle] |
| **Killed features** | [features that lost every round — these go on the kill list] |
| **Unfair advantage** | [extracted — this drives Phase 2 build priority] |
Extract killed features from fallen animals' insights. Each fallen animal likely attacked a weakness — the patches that stuck are strengths, the features that kept failing are dead.
Things that must be proven TRUE before writing any code. Each gate is a specific, binary test.
## Validation Gates — prove these before writing code
| Gate | Test | Pass if | Method |
|---|---|---|---|
| 1 | [specific test] | [measurable criterion] | [how to run the test] |
| 2 | [specific test] | [measurable criterion] | [how to run the test] |
| 3 | [specific test] | [measurable criterion] | [how to run the test] |
Rules:
Three phases. Each ends with a decision gate that determines whether to continue.
### Phase 1: Validate (Days 1-30)
| Week | Action |
|---|---|
| 1-2 | [specific validation activity tied to Gates 1-2] |
| 3-4 | [specific validation activity tied to Gates 3-5] |
**Decision gate:** [what must be true to proceed to Phase 2]
### Phase 2: Build Core (Days 31-60)
| Week | Action |
|---|---|
| 5-6 | [build the ONE feature that proves the unfair advantage — nothing else] |
| 7-8 | [ship to real users, iterate based on actual usage data] |
**Decision gate:** [what must be true to proceed to Phase 3]
### Phase 3: Expand (Days 61-90)
| Week | Action |
|---|---|
| 9-10 | [second feature, chosen based on Phase 2 usage data] |
| 11-12 | [one distribution or growth experiment] |
**Decision gate:** [what must be true to continue investing past 90 days]
Rules:
Features that must never be built. Sourced from battle output.
## Never Build
| Feature | Killed by | Reason |
|---|---|---|
| [feature] | [animal in battle] | [one line from battle insight] |
| [feature] | — | no structural advantage, would dilute unfair advantage |
| [feature] | — | user asked about it but battle proved it unnecessary |
Rules:
Compressed block the user can paste into future sessions to resume planning.
## Action Log
Copy this block into future sessions to resume planning.
> **Date:** [date]
> **Battle date:** [battle date if available]
> **Phase:** [1/2/3] | **Status:** [NOT STARTED / IN PROGRESS / GATE PASSED / BLOCKED]
> **Completed:** [what's done]
> **Blocked on:** [what's stuck, if anything]
> **Next:** [the single immediate next action]
When a user pastes an Action Log back, pick up from where they left off. Update the phase, check gate status, and give the next concrete action.
Strong battle output (full Battle Log, multiple rounds, clear apex predator):
Weak battle output (only Evolved Idea + Unfair Advantage, no Battle Log):
Battle killed the idea (no apex predator survived):
/food-chain-ideation with a pivot — the fallen animals' insights tell you what to change."Always output in this order:
No preamble. No disclaimers. Start with BATTLE DEBRIEF immediately after parsing input.
Every line in the output is something the user can act on today.
npx claudepluginhub codedrichy/food-chain-ideation --plugin food-chain-ideationProvides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.