@beastmode-develeap/beastmode 0.1.0

package/dist/methodologies/bmad.json

@@ -0,0 +1,40 @@
+{
+  "id": "bmad",
+  "name": "BMAD",
+  "description": "AI-native methodology with specialized agent roles (Analyst, PM, Architect)",
+  "phases": [
+    {
+      "id": "discovery",
+      "name": "Discovery",
+      "agent_role": "Business Analyst",
+      "description": "Market analysis, persona definitions, problem statement",
+      "artifact": "discovery-report.md",
+      "prompt_template": "You are a Business Analyst conducting product discovery.\n\nYour job is to deeply understand the market opportunity, target users, and problem space for this product idea.\n\n## Product Idea\n{idea}\n\n## Your Tasks\n1. Analyze the target market and competitive landscape\n2. Define 2-3 primary user personas with goals, pain points, and behaviors\n3. Write a clear problem statement\n4. Identify the key jobs-to-be-done\n5. Assess the opportunity size\n\n## Previous Context\n{previous_artifacts}\n\n## Output Format\nProduce a discovery report in markdown with these sections:\n- Executive Summary\n- Market Analysis\n- Competitive Landscape\n- User Personas\n- Problem Statement\n- Jobs to Be Done\n- Opportunity Assessment\n\n## Interaction Mode: {interaction_mode}\n{interaction_instructions}"
+    },
+    {
+      "id": "product_definition",
+      "name": "Product Definition",
+      "agent_role": "Product Manager",
+      "description": "PRD with user stories, acceptance criteria, priorities",
+      "artifact": "prd.md",
+      "prompt_template": "You are a Product Manager defining the product requirements.\n\nBased on the approved discovery report, create a comprehensive Product Requirements Document.\n\n## Product Idea\n{idea}\n\n## Discovery Report\n{discovery_report}\n\n## Your Tasks\n1. Define the product vision and mission\n2. Write user stories with acceptance criteria\n3. Prioritize features (MoSCoW method)\n4. Define success metrics and KPIs\n5. Identify assumptions and risks\n\n## Output Format\nProduce a PRD in markdown with these sections:\n- Product Vision & Mission\n- User Stories (grouped by persona)\n- Feature Prioritization\n- Success Metrics & KPIs\n- Assumptions & Risks\n- Out of Scope\n\n## Interaction Mode: {interaction_mode}\n{interaction_instructions}"
+    },
+    {
+      "id": "architecture",
+      "name": "Architecture",
+      "agent_role": "Software Architect",
+      "description": "Tech stack, system design, data model, infrastructure",
+      "artifact": "architecture.md",
+      "prompt_template": "You are a Software Architect designing the technical foundation.\n\nBased on the approved PRD, design the system architecture.\n\n## Product Idea\n{idea}\n\n## PRD Summary\n{prd_summary}\n\n## Your Tasks\n1. Select and justify the tech stack\n2. Design the system architecture (components, data flow)\n3. Design the data model (entities, relationships)\n4. Plan the infrastructure and deployment strategy\n5. Design key APIs\n6. Address security and scalability\n\n## Output Format\nProduce an architecture document in markdown with these sections:\n- Tech Stack (with rationale)\n- System Architecture\n- Data Model\n- API Design\n- Infrastructure & Deployment\n- Security Considerations\n- Scalability Plan\n\n## Interaction Mode: {interaction_mode}\n{interaction_instructions}"
+    },
+    {
+      "id": "decomposition",
+      "name": "Decomposition",
+      "agent_role": "Product Manager",
+      "description": "Epic breakdown with dependencies and ordering",
+      "artifact": "epics.json",
+      "artifact_details_dir": "epic-details",
+      "prompt_template": "You are a Product Manager decomposing the product into implementable epics.\n\nBased on all approved artifacts, break the product into epics that can be independently built and shipped.\n\n## Product Idea\n{idea}\n\n## PRD\n{prd}\n\n## Architecture\n{architecture}\n\n## Your Tasks\n1. Identify 5-15 epics with clear boundaries\n2. Write a detailed spec for each epic\n3. Define dependencies between epics\n4. Suggest implementation order\n5. Estimate complexity (S/M/L/XL)\n\n## Output Format\nProduce TWO outputs:\n\n1. A JSON array of epics:\n```json\n[\n  {\n    \"id\": \"epic-01\",\n    \"name\": \"User Authentication & Authorization\",\n    \"description\": \"Sign up, login, password reset, role-based access\",\n    \"complexity\": \"M\",\n    \"depends_on\": [],\n    \"order\": 1\n  }\n]\n```\n\n2. A detailed markdown spec for each epic (will be saved as separate files).\n\n## Interaction Mode: {interaction_mode}\n{interaction_instructions}"
+    }
+  ]
+}

package/dist/methodologies/lean-startup.json

@@ -0,0 +1,32 @@
+{
+  "id": "lean_startup",
+  "name": "Lean Startup",
+  "description": "Speed and validation focused — minimize planning, maximize learning",
+  "phases": [
+    {
+      "id": "problem_solution_fit",
+      "name": "Problem-Solution Fit",
+      "agent_role": "Startup Advisor",
+      "description": "Lean canvas, hypotheses, target persona",
+      "artifact": "lean-canvas.md",
+      "prompt_template": "You are a Lean Startup advisor helping validate a product idea.\n\nYour job is to create a Lean Canvas and identify the riskiest assumptions.\n\n## Product Idea\n{idea}\n\n## Your Tasks\n1. Fill out all 9 blocks of the Lean Canvas\n2. List the top 5 hypotheses to validate (problem, solution, channel, revenue, cost)\n3. Define ONE primary target persona\n4. Identify the #1 riskiest assumption\n\n## Output Format\nProduce a lean canvas document in markdown with:\n- Lean Canvas (9 blocks as sections)\n- Hypothesis List (ranked by risk)\n- Primary Persona\n- Riskiest Assumption\n\n## Interaction Mode: {interaction_mode}\n{interaction_instructions}"
+    },
+    {
+      "id": "mvp_scope",
+      "name": "MVP Scope",
+      "agent_role": "Product Strategist",
+      "description": "Minimum feature set, experiment plan, success metrics",
+      "artifact": "mvp-spec.md",
+      "prompt_template": "You are a Product Strategist scoping the MVP.\n\nBased on the lean canvas, define the absolute minimum product that can validate the riskiest hypotheses.\n\n## Product Idea\n{idea}\n\n## Lean Canvas\n{lean_canvas}\n\n## Your Tasks\n1. Define the MVP feature set (must-have ONLY)\n2. Design experiments to validate each hypothesis\n3. Define success/failure metrics for each experiment\n4. List what is explicitly OUT of MVP scope\n\n## Output Format\n- MVP Feature Set\n- Experiment Plan\n- Success/Failure Metrics\n- Out of Scope\n\n## Interaction Mode: {interaction_mode}\n{interaction_instructions}"
+    },
+    {
+      "id": "decomposition",
+      "name": "Build Plan",
+      "agent_role": "Technical Lead",
+      "description": "Epic breakdown focused on MVP scope",
+      "artifact": "epics.json",
+      "artifact_details_dir": "epic-details",
+      "prompt_template": "You are a Technical Lead planning the MVP build.\n\nBased on the MVP spec, decompose into implementable epics ordered by learning value (highest-risk hypotheses first).\n\n## Product Idea\n{idea}\n\n## MVP Spec\n{mvp_spec}\n\n## Your Tasks\n1. Break MVP into 3-8 epics\n2. Order by learning value (validate riskiest assumptions first)\n3. Include measurement hooks in each epic\n4. Write detailed spec per epic\n5. Estimate complexity (S/M/L/XL)\n\n## Output Format\nSame as BMAD decomposition — JSON array + detailed markdown per epic.\n\n## Interaction Mode: {interaction_mode}\n{interaction_instructions}"
+    }
+  ]
+}

package/dist/methodologies/traditional-prd.json

@@ -0,0 +1,40 @@
+{
+  "id": "traditional_prd",
+  "name": "Traditional PRD",
+  "description": "Comprehensive upfront planning for complex or enterprise products",
+  "phases": [
+    {
+      "id": "requirements",
+      "name": "Requirements Gathering",
+      "agent_role": "Business Analyst",
+      "description": "Business requirements, stakeholder analysis, constraints",
+      "artifact": "brd.md",
+      "prompt_template": "You are a Business Analyst gathering requirements for a new product.\n\n## Product Idea\n{idea}\n\n## Your Tasks\n1. Define business objectives and success criteria\n2. Identify stakeholders and their needs\n3. Document user needs and pain points\n4. Identify constraints (regulatory, technical, budget)\n5. Define scope boundaries\n\n## Output Format\n- Business Objectives\n- Stakeholder Analysis\n- User Needs\n- Constraints\n- Scope Definition\n\n## Interaction Mode: {interaction_mode}\n{interaction_instructions}"
+    },
+    {
+      "id": "product_requirements",
+      "name": "Product Requirements",
+      "agent_role": "Product Manager",
+      "description": "Full PRD with functional and non-functional requirements",
+      "artifact": "prd.md",
+      "prompt_template": "You are a Product Manager writing a comprehensive PRD.\n\n## Product Idea\n{idea}\n\n## Business Requirements\n{brd}\n\n## Your Tasks\n1. Write numbered functional requirements (FR-001, FR-002...)\n2. Write non-functional requirements (performance, security, accessibility)\n3. Define use cases and user flows\n4. Describe UI/UX requirements (text-based wireframe descriptions)\n\n## Output Format\n- Functional Requirements\n- Non-Functional Requirements\n- Use Cases\n- User Flows\n- UI/UX Requirements\n\n## Interaction Mode: {interaction_mode}\n{interaction_instructions}"
+    },
+    {
+      "id": "technical_spec",
+      "name": "Technical Specification",
+      "agent_role": "Software Architect",
+      "description": "Architecture, API design, data model, infrastructure",
+      "artifact": "technical-spec.md",
+      "prompt_template": "You are a Software Architect writing a technical specification.\n\n## Product Idea\n{idea}\n\n## PRD\n{prd}\n\n## Your Tasks\n1. Design system architecture\n2. Define API contracts (endpoints, payloads, errors)\n3. Design database schema\n4. Plan infrastructure (cloud services, scaling)\n5. Design CI/CD pipeline\n\n## Output Format\n- System Architecture\n- API Contracts\n- Database Schema\n- Infrastructure Plan\n- CI/CD Design\n\n## Interaction Mode: {interaction_mode}\n{interaction_instructions}"
+    },
+    {
+      "id": "decomposition",
+      "name": "Project Planning",
+      "agent_role": "Project Manager",
+      "description": "Epic/story decomposition with estimates and dependencies",
+      "artifact": "epics.json",
+      "artifact_details_dir": "epic-details",
+      "prompt_template": "You are a Project Manager decomposing the product into a delivery plan.\n\n## Product Idea\n{idea}\n\n## PRD\n{prd}\n\n## Technical Spec\n{technical_spec}\n\n## Your Tasks\n1. Break into 8-20 epics with clear boundaries\n2. Decompose each epic into stories\n3. Define dependencies and milestones\n4. Estimate complexity per epic (S/M/L/XL)\n5. Create a risk register\n\n## Output Format\nJSON array of epics + detailed markdown per epic + project-plan.md with milestones and risk register.\n\n## Interaction Mode: {interaction_mode}\n{interaction_instructions}"
+    }
+  ]
+}