feat: Add VentureArchitect AgentKit#225
Open
shaktiswain07 wants to merge 3 commits into
Open
Conversation
Contributor
|
Important Review skippedNo new commits to review since the last review. ⚙️ Run configurationConfiguration used: Repository UI (base), Organization UI (inherited) Review profile: ASSERTIVE Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
WalkthroughChangesThe VentureArchitect kit adds a Lamatic workflow that accepts startup inputs, generates structured venture-blueprint JSON, and packages the agent with prompts, model settings, metadata, documentation, a companion app scaffold, and repository configuration. VentureArchitect agent
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
akshatvirmani
changed the title
Contributor
:robot_face: AgentKit Structural ValidationNew Contributions Detected
Check Results
|
Contributor
|
Failure recorded at 2026-07-13T11:38:04Z UTC. If this PR is not fixed within 4 weeks it will be automatically closed. |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 10
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@kits/venture-architect/agent.md`:
- Around line 41-47: Resolve the broken scripts/ references across agent.md,
README.md, and flows/venture-architect.ts by either adding the referenced
validation and JSON-parsing script files under scripts/ or removing/updating
every reference to match the available implementation. Ensure the documented
pipeline remains accurate and actionable.
In `@kits/venture-architect/flows/venture-architect.ts`:
- Line 61: The venture-architect flow references missing scripts in its codeNode
steps. Add the scripts named venture-architect_ValidateInputs.ts,
venture-architect_BuildPrompt.ts, and venture-architect_JSONParser.ts under the
expected `@scripts` location, or update the references in the venture-architect
flow to existing script files; ensure all referenced codeNode paths resolve at
runtime.
In `@kits/venture-architect/flows/venturearchitect/config.json`:
- Around line 34-44: Replace the inlined system prompt content in the prompt
identified by id 187c2f4b-c23d-4545-abef-73dc897d6b7b with a reference to the
existing `@prompts/venture-architect_VentureArchitectLLM_system.md` external
prompt, preserving the system role and prompt configuration. Do not modify the
user prompt or duplicate the system prompt text in config.json.
- Around line 8-12: Update the trigger node’s advance_schema in the values
configuration to describe the documented input contract, including idea,
industry, audience, budget, timeline, and team_size, using the expected schema
format and field types.
- Around line 70-77: Update the API Response node’s outputMapping to map the
LLMNode_284 generated output, following the established flowOutput mapping
pattern used by execute-flow, instead of leaving it as an empty object.
- Around line 40-44: Update the user message content in the venture architect
configuration to reference the rendered result from BuildPrompt, such as
{{BuildPrompt.output}}, instead of embedding the buildPrompt TypeScript source.
Preserve the workflow’s expected prompt output as the input sent to the LLM.
In `@kits/venture-architect/flows/venturearchitect/meta.json`:
- Around line 1-9: Update the VentureArchitect metadata object in meta.json by
copying the rich description and eight tags from lamatic.config.ts, and populate
testInput with the kit’s supported test input so in-Studio testing works; leave
the URL fields unchanged unless corresponding kit-level values exist.
In `@kits/venture-architect/lamatic.config.ts`:
- Around line 24-37: Update the links configuration around demo to remove the
placeholder URL and its TODO comment, or replace them with a verified real demo
URL before merge. Keep the remaining github, deploy, and docs links unchanged.
In `@kits/venture-architect/README.md`:
- Around line 118-136: Update the README “Files” tree to include the exported
flows/venturearchitect/ package and list its config.json, inputs.json,
meta.json, and README.md files alongside flows/venture-architect.ts, matching
the package layout users receive.
- Around line 1-3: Change the “AI Venture Architecture Agent” heading in the
README from H3 to H2, preserving its text and the existing H1 title so the
document follows a valid H1 → H2 hierarchy.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI (base), Organization UI (inherited)
Review profile: ASSERTIVE
Plan: Pro
Run ID: 8a2a2b3e-a155-438f-9ec1-ca0a9fd51da3
📒 Files selected for processing (12)
kits/venture-architect/.gitignorekits/venture-architect/README.mdkits/venture-architect/agent.mdkits/venture-architect/constitutions/default.mdkits/venture-architect/flows/venture-architect.tskits/venture-architect/flows/venturearchitect/README.mdkits/venture-architect/flows/venturearchitect/config.jsonkits/venture-architect/flows/venturearchitect/inputs.jsonkits/venture-architect/flows/venturearchitect/meta.jsonkits/venture-architect/lamatic.config.tskits/venture-architect/model-configs/venture-architect_VentureArchitectLLM.tskits/venture-architect/prompts/venture-architect_VentureArchitectLLM_system.md
Comment on lines
+34
to
+44
| "prompts": [ | ||
| { | ||
| "id": "187c2f4b-c23d-4545-abef-73dc897d6b7b", | ||
| "role": "system", | ||
| "content": "You are VentureArchitect.\nYou are an experienced startup founder, product strategist, venture capital\nadvisor, software architect, and CTO. Your responsibility is to produce a\nfounder-ready venture blueprint from a raw idea.\nNever produce generic advice. Think step by step through the idea before\nyou answer: who has this problem, why existing options fall short, what the\nsmallest real version of this product looks like, and what it would\nactually cost and take to reach a first 100 users. Then produce your\nanswer.\nBe specific and realistic — grounded in the budget, timeline, and team size\ngiven. Favor a lean, buildable MVP over an over-scoped vision. Do not use\ngeneric filler; every field must read as if you actually thought about\nthis specific idea, not a template placeholder.\nReturn structured JSON only — no markdown fences, no commentary outside\nthe JSON object. Match exactly this shape:\n{\n \"startup_name\": \"A specific, brandable name (not generic)\",\n \"tagline\": \"One punchy sentence, under 12 words\",\n \"executive_summary\": \"3-4 sentences: what it is, who it's for, why now\",\n \"problem_statement\": \"2-3 sentences on the specific, painful problem\",\n \"solution\": \"2-3 sentences on how this product solves it\",\n \"target_users\": [\"Persona 1: short description\", \"Persona 2: short description\"],\n \"competitor_analysis\": [\n {\"name\": \"Competitor name\", \"description\": \"what they do\", \"gap\": \"what they miss that this startup addresses\"}\n ],\n \"revenue_model\": [\"Revenue stream 1 with rough pricing\", \"Revenue stream 2 with rough pricing\"],\n \"mvp_features\": [\"Feature 1\", \"Feature 2\", \"Feature 3\", \"Feature 4\"],\n \"tech_stack\": {\n \"frontend\": [\"Tech 1\"],\n \"backend\": [\"Tech 1\"],\n \"database\": [\"Tech 1\"],\n \"ai_ml\": [\"Tech 1\"],\n \"deployment\": [\"Tech 1\"]\n },\n \"database_design\": \"Plain-text description of the key tables/collections and their important fields\",\n \"api_suggestions\": [\"Service name - what it's used for\", \"Service name - what it's used for\"],\n \"folder_structure\": [\"frontend/\", \"backend/\", \"backend/routes/\", \"requirements.txt\", \"README.md\"],\n \"roadmap\": [\n {\"phase\": \"Phase name matching the given timeline\", \"tasks\": \"What gets built/done in this phase\"}\n ],\n \"cost_estimation\": {\n \"items\": [\n {\"item\": \"Cost category (e.g. Hosting, AI API costs)\", \"estimate\": \"$X/month or $X one-time\"}\n ],\n \"total_estimate\": \"Realistic total range given the stated budget\"\n },\n \"success_metrics\": [\n {\"metric\": \"Monthly Active Users\", \"target\": \"Specific, realistic target for month 3\"},\n {\"metric\": \"Retention (Day 30)\", \"target\": \"...\"},\n {\"metric\": \"Revenue\", \"target\": \"...\"},\n {\"metric\": \"Conversion Rate\", \"target\": \"...\"}\n ],\n \"risk_assessment\": [\n {\"risk\": \"A specific, realistic risk for this idea\", \"mitigation\": \"A concrete way to reduce or manage it\"}\n ],\n \"launch_checklist\": [\n \"Validate the idea with real target users\",\n \"Buy the domain\",\n \"Register the company\",\n \"Build the MVP\",\n \"Deploy\",\n \"Launch on Product Hunt or a relevant channel\",\n \"Start marketing\",\n \"Reach first 100 users\"\n ],\n \"next_30_day_plan\": [\n {\"week\": \"Week 1\", \"focus\": \"Specific, concrete focus for this week\"},\n {\"week\": \"Week 2\", \"focus\": \"...\"},\n {\"week\": \"Week 3\", \"focus\": \"...\"},\n {\"week\": \"Week 4\", \"focus\": \"...\"}\n ],\n \"investor_pitch\": \"A tight 4-6 sentence elevator pitch a founder could say out loud in 30 seconds: hook, problem, solution, market angle, ask.\",\n \"resume_description\": \"1-2 punchy resume bullet sentences starting with an action verb, mentioning the tech stack and role.\"\n}\nNever leave a field generic or empty — every field must reflect the\nspecific idea given." | ||
| }, | ||
| { | ||
| "id": "187c2f4b-c23d-4545-abef-73dc897d6b7d", | ||
| "role": "user", | ||
| "content": "export default function buildPrompt(inputs: ValidatedInputs): string {\nreturn `Raw idea: ${inputs.idea}\nIndustry: ${inputs.industry}\nTarget audience: ${inputs.audience}\nBudget available: ${inputs.budget}\nTimeline to launch: ${inputs.timeline}\nTeam size: ${inputs.team_size}\nTurn this into a venture blueprint following the JSON shape defined in\nyour instructions.`;\n}" | ||
| } |
Contributor
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟠 Major | ⚡ Quick win
System prompt is inlined — violates prompt externalization guideline.
The full system prompt text is embedded directly in config.json (lines 37-38) despite an externalized copy existing at prompts/venture-architect_VentureArchitectLLM_system.md. Per coding guidelines, prompts must be externalized into separate Markdown files in the prompts/ directory instead of being inlined in flow nodes. The .ts flow file should reference @prompts/venture-architect_VentureArchitectLLM_system.md and this inlined copy should be removed or replaced with a reference.
As per coding guidelines: "Prompts must be externalized into separate Markdown files in the prompts/ directory instead of being inlined in flow nodes."
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@kits/venture-architect/flows/venturearchitect/config.json` around lines 34 -
44, Replace the inlined system prompt content in the prompt identified by id
187c2f4b-c23d-4545-abef-73dc897d6b7b with a reference to the existing
`@prompts/venture-architect_VentureArchitectLLM_system.md` external prompt,
preserving the system role and prompt configuration. Do not modify the user
prompt or duplicate the system prompt text in config.json.
Source: Coding guidelines
Contributor
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@kits/venture-architect/agent.md`:
- Around line 51-54: Update the flow configuration reference in agent.md to use
the actual venturearchitect directory name, flows/venturearchitect/config.json,
and keep the existing node-wiring description unchanged.
In `@kits/venture-architect/README.md`:
- Around line 91-110: Update every README reference to the flow directory from
flows/venture-architect/ to flows/venturearchitect/, including the config.json
import path, meta.json testInput reference, and file-tree documentation;
preserve the existing flow instructions and node wiring details.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI (base), Organization UI (inherited)
Review profile: ASSERTIVE
Plan: Pro
Run ID: c0dc6ebb-43e5-4eef-8e15-78d13b02b37a
📒 Files selected for processing (8)
kits/venture-architect/README.mdkits/venture-architect/agent.mdkits/venture-architect/constitutions/default.mdkits/venture-architect/flows/venturearchitect/README.mdkits/venture-architect/flows/venturearchitect/config.jsonkits/venture-architect/flows/venturearchitect/inputs.jsonkits/venture-architect/flows/venturearchitect/meta.jsonkits/venture-architect/lamatic.config.ts
💤 Files with no reviewable changes (1)
- kits/venture-architect/lamatic.config.ts
Contributor
|
@coderabbitai review |
Contributor
✅ Action performedReview finished.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PR Checklist
1. Select Contribution Type
kits/<category>/<kit-name>/)bundles/<bundle-name>/)templates/<template-name>/)2. General Requirements
kebab-caseand matches the flow IDREADME.md(purpose, setup, usage)3. File Structure (Check what applies)
config.jsonpresent with valid metadata (name, description, tags, steps, author, env keys)flows/<flow-name>/(where applicable) include:config.json(Lamatic flow export)inputs.jsonmeta.jsonREADME.md.env.examplewith placeholder values only (kits only)config.jsonnode graphs (changes via Lamatic Studio export)4. Validation
npm install && npm run devworks locally (kits: UI runs; bundles/templates: flows are valid)[kit] Add <name> for <use case>)kits/venture-architect/(agent docs/guardrails + Lamatic template + model config + prompts + flow wiring + companion app stub).kits/venture-architect/.gitignorekits/venture-architect/.env.examplekits/venture-architect/README.mdkits/venture-architect/agent.mdkits/venture-architect/constitutions/default.mdkits/venture-architect/lamatic.config.tskits/venture-architect/model-configs/venture-architect_VentureArchitectLLM.tskits/venture-architect/prompts/venture-architect_VentureArchitectLLM_system.mdkits/venture-architect/apps/package.jsonkits/venture-architect/apps/.env.examplekits/venture-architect/flows/venture-architect.tskits/venture-architect/flows/venturearchitect/README.mdkits/venture-architect/flows/venturearchitect/config.jsonkits/venture-architect/flows/venturearchitect/inputs.jsonkits/venture-architect/flows/venturearchitect/meta.jsonkits/venture-architect/flows/venturearchitect/config.json) node types introduced:triggerNode(triggerNode_1)dynamicNode(LLMNode_284)responseNode(responseNode_triggerNode_1)triggerNode_1accepts theadvance_schemainputs (idea,industryrequired;audience,budget,timeline,team_sizeoptional).LLMNode_284generates the venture blueprint using the referenced system prompt + a user prompt template that injects the trigger inputs; output is requested/returned as JSON.responseNode_triggerNode_1returnsresult(mapped fromLLMNode_284output) withcontent-type: application/json.triggerNode_1 → LLMNode_284 → responseNode_triggerNode_1, plus a directresponseEdgefromtriggerNode_1toresponseNode_triggerNode_1.