Skill

timeline-and-project

Produce a milestone-based timeline and project plan for taking an idea from today to first paying customer (or first deployment). Identifies critical path, parallelisable workstreams, and key checkpoints. Use when the user wants to know "what's the realistic path and how long".

npx claudepluginhub danielrosehill/claude-code-plugins --plugin business-idea-eval

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Translate an idea + dev spec into an executable project plan with honest durations.

SKILL.md

Similar Skills

skill-lookup

159.9k

Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.

prompts.chat

next-compile

139.2k

Checks Next.js compilation errors using a running Turbopack dev server after code edits. Fixes actionable issues before reporting complete. Replaces `next build`.

1 file

vercel-next-js-2

angular-new-app

100.1k

Creates new Angular apps using Angular CLI with flags for routing, SSR, SCSS, prefixes, and AI config. Follows best practices for modern TypeScript/Angular development. Use when starting Angular projects.

angular-angular-1

Stats

Stars0

Forks0

Last CommitApr 28, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

timeline-and-project

Timeline & Project Plan

Translate an idea + dev spec into an executable project plan with honest durations.

Steps

Read the idea, dev spec (or hardware feasibility), assumptions output.

Define the target milestone — typically "first paying customer" for B2C/B2B SaaS, "first pilot deployment" for hardware/enterprise, "first 1000 active users" for consumer.

Lay out the path as a sequence of milestones, e.g.:

M1: validate top assumption (week 1–2)
M2: MVP feature-complete in dev (week 3–8)
M3: closed beta with N users (week 9–12)
M4: paid launch (week 13–16) For each milestone: deliverables, exit criteria, dependencies.

Identify the critical path — what blocks each milestone. Call out any single-threaded bottleneck.

Identify parallelisable workstreams — branding/positioning, customer development, partnership conversations, regulatory prep — that can run alongside engineering.

Note decision gates — points where the user should re-evaluate continuing (e.g. after M1: did the assumption validate? if not, kill or pivot).

Output

<workspace_path>/ideas/<slug>/analysis/timeline-and-project.md with frontmatter:

--- lens: timeline-and-project generated: YYYY-MM-DD target_milestone: <text> target_weeks: <number> critical_path: <short summary> ---

Notes

Be honest about durations. Solo founder building part-time goes 3-5x slower than a funded team.

Always include a kill criterion. Plans without a kill criterion become endless.

Timeline & Project Plan

Translate an idea + dev spec into an executable project plan with honest durations.

Steps

Read the idea, dev spec (or hardware feasibility), assumptions output.
Define the target milestone — typically "first paying customer" for B2C/B2B SaaS, "first pilot deployment" for hardware/enterprise, "first 1000 active users" for consumer.
Lay out the path as a sequence of milestones, e.g.:
- M1: validate top assumption (week 1–2)
- M2: MVP feature-complete in dev (week 3–8)
- M3: closed beta with N users (week 9–12)
- M4: paid launch (week 13–16) For each milestone: deliverables, exit criteria, dependencies.
Identify the critical path — what blocks each milestone. Call out any single-threaded bottleneck.
Identify parallelisable workstreams — branding/positioning, customer development, partnership conversations, regulatory prep — that can run alongside engineering.
Note decision gates — points where the user should re-evaluate continuing (e.g. after M1: did the assumption validate? if not, kill or pivot).

Output

<workspace_path>/ideas/<slug>/analysis/timeline-and-project.md with frontmatter:

---
lens: timeline-and-project
generated: YYYY-MM-DD
target_milestone: <text>
target_weeks: <number>
critical_path: <short summary>
---

Notes

Be honest about durations. Solo founder building part-time goes 3-5x slower than a funded team.
Always include a kill criterion. Plans without a kill criterion become endless.