AgentStack
SKILL verified MIT Self-run

Startup Product Development

skill-wrm3-ai-project-template-startup-product-development · by wrm3

A Claude skill from wrm3/ai_project_template.

No reviews yet
0 installs
2 views
0.0% view→install

Install

$ agentstack add skill-wrm3-ai-project-template-startup-product-development

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Startup Product Development? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Startup Product Development Skill

> Industry-Agnostic Product Strategy & Execution Framework > For software, hardware, biotech, consumer products, and B2B services

Overview

This skill provides comprehensive product development guidance for startups across ALL industries. This is NOT code development (we have SubAgents for that) - this is PRODUCT STRATEGY, roadmap planning, MVP definition, quality assurance frameworks, and revolutionary concept exploration.

What This Skill Covers:

  • MVP (Minimum Viable Product) definition and scoping
  • Product roadmap planning and prioritization
  • Technology stack selection by industry
  • Industry-specific development processes
  • Quality assurance frameworks
  • Revolutionary concept exploration
  • Build vs buy decisions
  • Product-market fit assessment

Industries Supported:

  • Software/SaaS (web, mobile, cloud, AI/ML)
  • Hardware (IoT, electronics, robotics, consumer devices)
  • Biotech/Pharma (diagnostics, therapeutics, medical devices)
  • Consumer Products (CPG, retail, food & beverage)
  • B2B Services (platforms, consulting, enterprise tools)

When to Use This Skill

Automatic Triggers

Use this skill automatically when user mentions:

  • "product roadmap"
  • "MVP" or "minimum viable product"
  • "product development plan"
  • "technology stack"
  • "what should I build first"
  • "product-market fit"
  • "revolutionary product"
  • Industry-specific: "prototype", "clinical trials", "manufacturing"

Manual Invocation

  • User explicitly asks for product development guidance
  • User needs help defining MVP scope
  • User wants to create a product roadmap
  • User needs technology stack recommendations
  • User is exploring revolutionary concepts

NOT for This Skill

  • Code implementation (use full-stack-developer, backend-developer, frontend-developer SubAgents)
  • Bug fixing (use debugger SubAgent)
  • Code review (use code-reviewer SubAgent)
  • Infrastructure setup (use devops-engineer SubAgent)

Core Capabilities

1. MVP Definition

Purpose: Define the absolute minimum product that delivers core value

Process:

  1. Identify core problem being solved
  2. List essential features (must-have)
  3. Distinguish nice-to-have features
  4. Define success metrics
  5. Estimate timeline and resources

Anti-Patterns to Avoid:

  • Scope creep (adding "just one more feature")
  • Building for scale before validation
  • Perfecting UX before testing core value
  • Including features for edge cases
  • Building full feature set before launch

Reference: See reference/mvp_definition.md

2. Product Roadmap Planning

Purpose: Strategic plan from vision to execution

Framework: Vision → Strategy → Roadmap → Backlog

Roadmap Structure:

  • Quarterly themes (Q1-Q4)
  • Monthly milestones
  • Feature prioritization
  • Resource allocation
  • Risk mitigation

Prioritization Methods:

  • RICE: Reach × Impact × Confidence ÷ Effort
  • MoSCoW: Must have, Should have, Could have, Won't have
  • Kano Model: Basic, Performance, Excitement features
  • Value vs Effort Matrix: Quick wins, major projects, fill-ins, time sinks

Reference: See reference/product_roadmap_planning.md

3. Technology Stack Selection

Purpose: Choose optimal technologies for your industry and scale

Software/SaaS Stack Decisions:

  • Frontend: React, Vue, Angular, Next.js, React Native, Flutter
  • Backend: Node.js, Python (Django/Flask), Go, Java (Spring), Ruby (Rails)
  • Database: PostgreSQL, MySQL, MongoDB, DynamoDB, Firebase
  • Hosting: AWS, GCP, Azure, Vercel, Netlify, Railway
  • Infrastructure: Docker, Kubernetes, Serverless, Edge computing

Hardware Stack Decisions:

  • Microcontrollers: Arduino, Raspberry Pi, ESP32, STM32
  • Connectivity: WiFi, Bluetooth, LoRa, Zigbee, Cellular (4G/5G)
  • Sensors: Temperature, motion, pressure, optical, chemical
  • Power: Battery (Li-ion, LiPo), solar, USB-C PD, wireless charging
  • Enclosure: 3D printing, injection molding, CNC machining

Biotech Stack Decisions:

  • Lab Equipment: PCR, sequencing, mass spec, flow cytometry
  • Reagents: Enzymes, antibodies, cell lines, media
  • Analysis Software: Bioinformatics pipelines, statistical tools
  • Data Management: LIMS, ELN, cloud storage, compliance systems

Decision Framework:

  1. Current requirements
  2. Future scalability
  3. Team expertise
  4. Budget constraints
  5. Time to market
  6. Ecosystem maturity
  7. Community support

Reference: See reference/tech_stack_selection.md

4. Industry-Specific Development

Software/SaaS Development

Methodology: Agile/Scrum for startups

  • 2-week sprints
  • Daily standups (async for small teams)
  • Sprint planning, review, retrospective
  • Continuous integration/deployment (CI/CD)

Development Phases:

  1. Planning: User stories, acceptance criteria
  2. Design: Wireframes, mockups, prototypes
  3. Development: Code, test, review
  4. Testing: Unit, integration, E2E, UAT
  5. Deployment: Staging → Production
  6. Monitoring: Analytics, error tracking, performance

Key Practices:

  • Version control (Git + GitHub/GitLab)
  • Code reviews
  • Automated testing
  • Feature flags
  • A/B testing
  • Analytics integration

Reference: See reference/software_development_guide.md

Hardware Development

Development Phases:

  1. Concept: Sketches, block diagrams, requirements
  2. Prototype: Breadboard, proof of concept
  3. Engineering: Schematic design, PCB layout, firmware
  4. Pre-production: DFM review, tooling, pilot run
  5. Manufacturing: Mass production, quality control
  6. Distribution: Packaging, shipping, support

Critical Considerations:

  • PCB Design: 2-layer vs 4-layer, component placement, signal integrity
  • Enclosure: CAD design, material selection, IP rating
  • Firmware: Embedded C/C++, OTA updates, power management
  • Certifications: FCC (US), CE (EU), UL (safety), IP ratings
  • Supply Chain: Component sourcing, lead times, alternatives
  • Manufacturing: Domestic vs overseas, MOQ, cost per unit

Key Milestones:

  • Breadboard working prototype (Week 4-8)
  • PCB Rev 1 (Week 8-12)
  • Enclosure CAD complete (Week 12-16)
  • Pre-production units (Week 20-24)
  • Manufacturing pilot run (Week 28-32)

Reference: See reference/hardware_development_guide.md

Biotech/Pharma Development

Development Phases:

  1. Discovery: Literature review, hypothesis generation
  2. Assay Development: In vitro testing, validation
  3. Preclinical: Animal studies, safety testing
  4. Clinical Trials: Phase I (safety), II (efficacy), III (confirmation)
  5. Regulatory: FDA submission (510(k), PMA, De Novo, IND, NDA)
  6. Manufacturing: GMP facility, scale-up, quality systems

Critical Considerations:

  • IP Strategy: Patents on composition, method, use
  • Regulatory Pathway: 510(k) (Class II), PMA (Class III), De Novo (novel Class II)
  • Clinical Trial Design: Endpoints, patient population, statistical power
  • GMP Requirements: Manufacturing processes, quality control, documentation
  • Reimbursement: CPT codes, payer coverage, health economics

Timeline Realities:

  • Diagnostics: 3-5 years to market
  • Medical devices: 3-7 years to market
  • Therapeutics: 8-15 years to market
  • Cost: $5M-$50M+ depending on complexity

Reference: See reference/biotech_development_guide.md

Consumer Products Development

Development Phases:

  1. Ideation: Consumer insights, trend analysis
  2. Concept Testing: Focus groups, surveys, prototypes
  3. Design: Industrial design, packaging, branding
  4. Sampling: Prototypes, user testing, iteration
  5. Manufacturing: Partner selection, quality standards
  6. Launch: Distribution, marketing, retail placement

Critical Considerations:

  • User-Centered Design: Pain points, desires, behaviors
  • Rapid Prototyping: 3D printing, mockups, MVP samples
  • Manufacturing Partners: Alibaba, ThomasNet, local manufacturers
  • Packaging: Shelf appeal, sustainability, cost
  • Distribution: DTC (Shopify), Amazon, retail buyers
  • Margins: 3-5x manufacturing cost for retail

Key Metrics:

  • Customer acquisition cost (CAC)
  • Lifetime value (LTV)
  • Conversion rate
  • Repeat purchase rate
  • Net promoter score (NPS)

5. Quality Assurance Frameworks

Purpose: Ensure product quality before and after launch

Testing Strategies by Industry:

Software/SaaS:

  • Unit Tests: Function/method level (80%+ coverage)
  • Integration Tests: API endpoints, database interactions
  • E2E Tests: User workflows (Cypress, Playwright, Selenium)
  • Performance Tests: Load testing, stress testing
  • Security Tests: Penetration testing, vulnerability scans
  • User Acceptance Testing (UAT): Beta users, feedback loops

Hardware:

  • Functional Testing: Does it work as specified?
  • Environmental Testing: Temperature, humidity, drop tests
  • Reliability Testing: MTBF (mean time between failures)
  • Compliance Testing: FCC, CE, UL, IP ratings
  • Manufacturing Testing: In-circuit test (ICT), functional test
  • Field Testing: Beta units with real users

Biotech:

  • Analytical Validation: Sensitivity, specificity, accuracy, precision
  • Clinical Validation: Clinical trials, real-world evidence
  • Manufacturing Validation: Process validation, batch consistency
  • Stability Testing: Shelf life, storage conditions
  • Quality Control: Every batch, statistical process control
  • Regulatory Compliance: FDA QSR, ISO 13485

QA Metrics:

  • Defect density (bugs per 1000 lines of code or per unit)
  • Test coverage (% code/features tested)
  • Mean time to resolution (MTTR)
  • Escaped defects (found in production)
  • Customer satisfaction (CSAT, NPS)

Reference: See reference/quality_assurance_frameworks.md

6. Revolutionary Concept Exploration

Purpose: Validate and develop breakthrough innovations

Innovation Frameworks:

First Principles Thinking:

  1. Break down problem to fundamental truths
  2. Question all assumptions
  3. Rebuild solution from ground up
  4. Example: SpaceX reusable rockets vs traditional expendable

Design Thinking Process:

  1. Empathize: Deep user understanding
  2. Define: Problem statement
  3. Ideate: Brainstorm solutions
  4. Prototype: Quick mockups
  5. Test: Validate with users

TRIZ (Theory of Inventive Problem Solving):

  • 40 inventive principles
  • Contradiction resolution
  • Technology evolution trends
  • Used by Samsung, Intel, NASA

Moonshot Validation:

  1. Technical Feasibility: Can it be built with existing/near-term tech?
  2. Market Validation: Do people actually need this?
  3. Business Model: Can it be profitable/sustainable?
  4. Competitive Moat: What prevents copying?
  5. Timeline: Can we build it before someone else?

Proof of Concept (PoC):

  • Build minimal technical demonstration
  • Validate core hypothesis
  • Test with target users
  • Measure key metrics
  • Decision point: Pivot, persevere, or kill

Reference: See reference/revolutionary_concept_guide.md

7. Build vs Buy Decisions

Framework:

Build When:

  • Core competitive differentiator
  • Unique requirements not met by existing solutions
  • Long-term cost savings justify upfront investment
  • Maintain control over roadmap and data
  • No suitable alternatives exist

Buy/Use Third-Party When:

  • Commodity functionality (auth, payments, email)
  • Well-established market solutions exist
  • Faster time to market critical
  • Not core to competitive advantage
  • Ongoing maintenance burden too high

Decision Matrix: | Factor | Weight | Build Score | Buy Score | |--------|--------|-------------|-----------| | Time to Market | 0.25 | 3/10 | 9/10 | | Cost (2 years) | 0.20 | 5/10 | 7/10 | | Competitive Advantage | 0.25 | 9/10 | 2/10 | | Maintenance Burden | 0.15 | 4/10 | 8/10 | | Flexibility/Control | 0.15 | 10/10 | 5/10 | | Weighted Total | 1.00 | 6.3/10 | 6.4/10 |

Common Buy Decisions for Startups:

  • Authentication: Auth0, Firebase Auth, AWS Cognito
  • Payments: Stripe, PayPal, Square
  • Email: SendGrid, Mailgun, AWS SES
  • Analytics: Mixpanel, Amplitude, Google Analytics
  • Error Tracking: Sentry, Rollbar, Bugsnag
  • Customer Support: Intercom, Zendesk, HubSpot

Template: See templates/build_vs_buy_template.xlsx

8. Product-Market Fit Assessment

Indicators of Product-Market Fit:

  • Users actively seeking your product (organic demand)
  • High retention rates (40%+ monthly retention)
  • Word-of-mouth growth (NPS > 50)
  • Users upset if product disappeared (Sean Ellis test: >40% "very disappointed")
  • Scaling challenges (too much demand)

Assessment Framework:

  1. Measure Core Metrics:
  • Retention cohorts (Day 1, 7, 30, 90)
  • Net Promoter Score (NPS)
  • Customer acquisition cost (CAC) vs Lifetime Value (LTV)
  • Churn rate
  • Organic vs paid growth
  1. Qualitative Signals:
  • Unsolicited testimonials
  • Press coverage requests
  • Investor inbound interest
  • Competitor reactions
  1. Decision Framework:
  • No PMF yet: Focus on iteration, user interviews, pivots
  • Early PMF: Double down on growth, optimize funnel
  • Strong PMF: Scale operations, expand team, raise capital

Reference: See Research & Validation Skill for detailed market research frameworks

Available Resources

Reference Guides (reference/)

  1. mvp_definition.md (~400 lines)
  • What is MVP?
  • How to define scope
  • Common MVP mistakes
  • Success metrics
  • Examples by industry
  1. productroadmapplanning.md (~450 lines)
  • Vision → Strategy → Roadmap → Backlog
  • Quarterly planning frameworks
  • Prioritization methods (RICE, MoSCoW, Kano)
  • Stakeholder alignment
  • Roadmap communication
  1. techstackselection.md (~500 lines)
  • Software/SaaS stack options
  • Hardware stack options
  • Biotech stack options
  • Decision frameworks
  • Migration considerations
  • Cost analysis
  1. softwaredevelopmentguide.md (~600 lines)
  • Agile/Scrum for startups
  • Sprint planning and execution
  • CI/CD pipelines
  • Testing strategies
  • Deployment best practices
  • Development tools
  1. hardwaredevelopmentguide.md (~550 lines)
  • Prototyping to manufacturing
  • PCB design principles
  • Enclosure design
  • Supply chain management
  • Regulatory approvals (FCC, CE, UL)
  • Quality control
  1. biotechdevelopmentguide.md (~600 lines)
  • R&D process
  • Clinical trial design
  • FDA regulatory pathways
  • GMP manufacturing
  • IP strategy
  • Reimbursement strategy
  1. qualityassuranceframeworks.md (~450 lines)
  • Testing strategies by industry
  • QA processes and metrics
  • Beta testing programs
  • Quality control systems
  • Continuous improvement
  1. revolutionaryconceptguide.md (~500 lines)
  • First principles thinking
  • Innovation frameworks (Design Thinking, TRIZ)
  • Moonshot validation
  • Technical feasibility assessment
  • Proof of concept development

Templates (templates/)

  1. mvpspectemplate.md
  • MVP feature list with priorities
  • Acceptance criteria
  • Success metrics
  • Timeline estimation
  1. productroadmaptemplate.md
  • Quarterly roadmap structure
  • Feature themes
  • Milestone definitions
  • Resource allocation
  1. techstackdecision_matrix.xlsx
  • Technology comparison spreadsheet
  • Weighted scoring
  • Cost analysis
  • Decision documentation
  1. sprintplanningtemplate.md
  • 2-week sprint structure
  • User stories format
  • Sprint goals and commitments
  • Retrospective format
  1. qualitychecklisttemplate.md
  • Pre-launch QA checklist
  • Testing coverage requirements
  • Release readiness criteria
  • By product type (software, hardware, biotech)
  1. innovationcanvastemplate.md
  • Revolutionary concept explo

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.