Plan Founder Review

Keep this short and decision-oriented.

3. Explicitly define scope

Always separate:

• In scope now
• Worth deferring
• Out of scope

If scope expands, say why. If scope shrinks, say what risk or waste is being avoided.

4. Prefer leverage over surface area

Recommend the version that improves outcome per unit of complexity.

Favor:

• reusable workflow over one-off patch
• source-of-truth change over manual repetition
• system improvement over cosmetic busywork
• closed loop over broad unfinished ambition

5. Name the key decision

End with one clear recommendation:

• Build the bigger version
• Build the smaller version
• Keep exact scope
• Do not build this; solve adjacent problem instead

Output format

Use this structure when helpful:

Real goal

One or two sentences.

Option A — Literal request

What it gives What it misses

Option B — Higher-leverage version

What it gives Why it may be better

Option C — Smallest closed loop

What can be proven quickly

Recommendation

Pick one and explain why.

Scope now

• In
• Defer
• Out

Heuristics

Push bigger when

• the same effort unlocks much more user value
• the request is obviously a proxy
• a reusable capability is one step away
• implementation cost is low but strategic upside is high

Shrink when

• the plan creates many moving parts without proving value
• the user mainly needs evidence, not infrastructure
• there is no clear success metric
• more scope increases fragility more than usefulness

Reject or redirect when

• the request optimizes the wrong metric
• it adds ceremony without leverage
• the process is unclear enough that building now is wasteful
• existing tools already solve the problem well enough

For DaddyTech workspace

Use this skill especially for:

• new skills
• agent workflow design
• publishing/automation pipelines
• content product ideas
• project kickoff decisions
• requests that sound clear technically but fuzzy strategically

Do not let implementation enthusiasm outrun product clarity.36:["$","$L3f",null,{"content":"$40","frontMatter":{"name":"plan-founder-review","description":"Reframe a request from founder/product-first perspective before execution. Use when the user asks for a new feature, workflow, automation, content product, agent skill, project plan, or any solution design where the literal request may hide a more valuable problem. Triggers on requests to plan, rethink scope, find the real goal, compare ambitious vs minimal versions, or decide what should and should not be built."}}]