Side Project Launcher — companyproject basis pipeline
ideaverify→tech stack→MVP→developmentroadmap→launchchecklist An agent team collaborates to generate all deliverables at once.
execution mode
agent team — 5 agents communicate directly via SendMessage and cross-verify each other's work.
agent composition
| agent |
file |
role |
type |
| idea-validator |
.claude/agents/idea-validator.md |
market analysis, competition research, differentiation verify |
general-purpose |
| techstack-analyst |
.claude/agents/techstack-analyst.md |
tech stack comparison, recommendation, person design |
general-purpose |
| mvp-designer |
.claude/agents/mvp-designer.md |
core feature definition, , |
general-purpose |
| roadmap-builder |
.claude/agents/roadmap-builder.md |
development schedule, launch strategy, checklist |
general-purpose |
| launch-reviewer |
.claude/agents/launch-reviewer.md |
cross-verification, execution possiblenature confirm |
general-purpose |
workflow
Phase 1: preparation (Orchestrator directly perform)
- Extract from user input:
- idea: , problem
- development competency (optional): usage possibleKorean technical, development level
- ** time** (optional): week deploy possible time
- budget (optional): month operations cost Korean
- existing file (optional): basisfrom, etc.
_workspace/ Create the directory at the project root
- Organize input and save to
_workspace/00_input.md
- If existing files are provided, copy them to
_workspace/and skip the corresponding Phase
- Determine the execution mode based on the scope of the request
Phase 2: team composition and execution
| order |
task |
responsible |
dependency |
deliverable |
| 1 |
idea verify |
validator |
None |
_workspace/01_idea_validation.md |
| 2 |
tech stack |
techstack |
task 1 |
_workspace/02_techstack_recommendation.md |
| 3 |
MVP design |
designer |
task 1, 2 |
_workspace/03_mvp_spec.md |
| 4 |
roadmap·launch |
roadmap |
task 2, 3 |
_workspace/04_roadmap_launch.md |
| 5 |
launch review |
reviewer |
task 1~4 |
_workspace/05_review_report.md |
teamKRW between flow:
- validator complete → techstackto project type·difficulty, designerto UVP·differentiation point, roadmapto market deliver
- techstack complete → designerto technical constraint·implementation difficulty, roadmapto learning time·technical risk deliver
- designer complete → roadmapto featureby time·priority deliver
- reviewer all deliverable cross-verification. 🔴 required revision findings when Request revision from the relevant agent -> rework -> re-verify (up to 2 rounds)
Phase 3: integration and final deliverable
_workspace/ Verify all files in the directory
- review reportConfirm that all critical revisions from the review report have been addressed
- Report the final summary to the user
task scaleby mode
| user request pattern |
execution mode |
deploy agent |
| "companyproject overall basis" |
Full pipeline |
5people beforeKRW |
| " idea verifyplease do" |
verify mode |
validator + reviewer |
| "tech stack recommendationplease do" (idea ) |
technical mode |
validator + techstack + reviewer |
| "MVP " (technical decision) |
MVP mode |
designer + roadmap + reviewer |
| "launch checklist create it" |
launch mode |
roadmap + reviewer |
existing file utilization: user basisfrom, tech stack decision etc. provide applicable stage case.
data deliver protocol
| strategy |
method |
also |
| File-based |
_workspace/ |
Store and share major deliverables |
| Message-based |
SendMessage |
Real-time key information transfer, revision requests |
| Task-based |
TaskCreate/TaskUpdate |
Progress tracking, dependency management |
File naming convention: {}_{agent}_{deliverable}.{extensionspecialist}
error handling
| error type |
strategy |
| idea un-present |
trend based idea 3items proposal after optional also |
| development None |
code/code recommendation, learning roadmap included |
| web search failure |
general market degreeas analysis, "data limitation" specify |
| agent failure |
Retry once -> proceed without that deliverable, note the gap in the review report |
| reviewfrom 🔴 findings |
Request revision from the relevant agent -> rework -> re-verify (up to 2 rounds) |
test scenario
flow
Prompt: "developmentspecialist interview preparation week web companyproject . React week developmentto do ."
expected result:
- verify: interview preparation market analysis, existing service(LeetCode, ) versus differentiation
- technical: React + Supabase + Vercel recommendation, free utilization
- MVP: core feature 3~5items, , data model
- roadmap: 4week sprint, Product Hunt launch strategy
- review: overall consistency verify, risk matrix
existing file utilization flow
Prompt: "un- idea verify tech stack also . MVP only " + basisfrom department
expected result:
- MVP mode: designer + roadmap + reviewer deploy
- validator, techstack case
error flow
Prompt: " reporting idea "
expected result:
- validator user company question or trend based idea 3items proposal
- optional after Full pipeline progress
- review report "idea stage" specify
agentby extension skill
| agent |
extension skill |
also |
| idea-validator |
market-sizing-calculator |
TAM/SAM/SOM calculation, revenue model verify |
| techstack-analyst |
techstack-decision-matrix |
tech stack comparison matrix, person cost total |
1---2name: side-project-launcher3description: companyproject basis A pipeline where an agent team collaborates for comprehensive planning. 'companyproject basis', 'company project idea', ' project', 'MVP ', ' reporting ', 'service launch', '1person development', 'indie hacking', 'week project', 'tech stack ', 'company ' etc. companyproject basis before skill usage. existing idea case also tech stack MVP design degreeKRW. However, actual code writing, specialistperson whenplan work, person/from versus is outside this skill's scope.4---56# Side Project Launcher — companyproject basis pipeline78ideaverify→tech stack→MVP→developmentroadmap→launchchecklist An agent team collaborates to generate all deliverables at once.910## execution mode1112**agent team** — 5 agents communicate directly via SendMessage and cross-verify each other's work.1314## agent composition1516| agent | file | role | type |17|---------|------|------|------|18| idea-validator | `.claude/agents/idea-validator.md` | market analysis, competition research, differentiation verify | general-purpose |19| techstack-analyst | `.claude/agents/techstack-analyst.md` | tech stack comparison, recommendation, person design | general-purpose |20| mvp-designer | `.claude/agents/mvp-designer.md` | core feature definition, , | general-purpose |21| roadmap-builder | `.claude/agents/roadmap-builder.md` | development schedule, launch strategy, checklist | general-purpose |22| launch-reviewer | `.claude/agents/launch-reviewer.md` | cross-verification, execution possiblenature confirm | general-purpose |2324## workflow2526### Phase 1: preparation (Orchestrator directly perform)27281. Extract from user input:29 - **idea**: , problem30 - **development competency** (optional): usage possibleKorean technical, development level31 - ** time** (optional): week deploy possible time32 - **budget** (optional): month operations cost Korean33 - **existing file** (optional): basisfrom, etc.342. `_workspace/` Create the directory at the project root353. Organize input and save to `_workspace/00_input.md`364. If existing files are provided, copy them to `_workspace/`and skip the corresponding Phase375. Determine the **execution mode** based on the scope of the request3839### Phase 2: team composition and execution4041| order | task | responsible | dependency | deliverable |42|------|------|------|------|--------|43| 1 | idea verify | validator | None | `_workspace/01_idea_validation.md` |44| 2 | tech stack | techstack | task 1 | `_workspace/02_techstack_recommendation.md` |45| 3 | MVP design | designer | task 1, 2 | `_workspace/03_mvp_spec.md` |46| 4 | roadmap·launch | roadmap | task 2, 3 | `_workspace/04_roadmap_launch.md` |47| 5 | launch review | reviewer | task 1~4 | `_workspace/05_review_report.md` |4849**teamKRW between flow:**50- validator complete → techstackto project type·difficulty, designerto UVP·differentiation point, roadmapto market deliver51- techstack complete → designerto technical constraint·implementation difficulty, roadmapto learning time·technical risk deliver52- designer complete → roadmapto featureby time·priority deliver53- reviewer all deliverable cross-verification. 🔴 required revision findings when Request revision from the relevant agent -> rework -> re-verify (up to 2 rounds)5455### Phase 3: integration and final deliverable56571. `_workspace/` Verify all files in the directory582. review reportConfirm that all critical revisions from the review report have been addressed593. Report the final summary to the user6061## task scaleby mode6263| user request pattern | execution mode | deploy agent |64|----------------|----------|-------------|65| "companyproject overall basis" | **Full pipeline** | 5people beforeKRW |66| " idea verifyplease do" | **verify mode** | validator + reviewer |67| "tech stack recommendationplease do" (idea ) | **technical mode** | validator + techstack + reviewer |68| "MVP " (technical decision) | **MVP mode** | designer + roadmap + reviewer |69| "launch checklist create it" | **launch mode** | roadmap + reviewer |7071**existing file utilization**: user basisfrom, tech stack decision etc. provide applicable stage case.7273## data deliver protocol7475| strategy | method | also |76|------|------|------|77| File-based | `_workspace/` | Store and share major deliverables |78| Message-based | SendMessage | Real-time key information transfer, revision requests |79| Task-based | TaskCreate/TaskUpdate | Progress tracking, dependency management |8081File naming convention: `{}_{agent}_{deliverable}.{extensionspecialist}`8283## error handling8485| error type | strategy |86|----------|------|87| idea un-present | trend based idea 3items proposal after optional also |88| development None | code/code recommendation, learning roadmap included |89| web search failure | general market degreeas analysis, "data limitation" specify |90| agent failure | Retry once -> proceed without that deliverable, note the gap in the review report |91| reviewfrom 🔴 findings | Request revision from the relevant agent -> rework -> re-verify (up to 2 rounds) |9293## test scenario9495### flow96**Prompt**: "developmentspecialist interview preparation week web companyproject . React week developmentto do ."97**expected result**:98- verify: interview preparation market analysis, existing service(LeetCode, ) versus differentiation99- technical: React + Supabase + Vercel recommendation, free utilization100- MVP: core feature 3~5items, , data model101- roadmap: 4week sprint, Product Hunt launch strategy102- review: overall consistency verify, risk matrix103104### existing file utilization flow105**Prompt**: "un- idea verify tech stack also . MVP only " + basisfrom department106**expected result**:107- MVP mode: designer + roadmap + reviewer deploy108- validator, techstack case109110### error flow111**Prompt**: " reporting idea "112**expected result**:113- validator user company question or trend based idea 3items proposal114- optional after Full pipeline progress115- review report "idea stage" specify116117## agentby extension skill118119| agent | extension skill | also |120|---------|----------|------|121| idea-validator | `market-sizing-calculator` | TAM/SAM/SOM calculation, revenue model verify |122| techstack-analyst | `techstack-decision-matrix` | tech stack comparison matrix, person cost total |