defprod-onboard-product

Builds a complete DefProd product definition from an existing codebase through phased MCP workflows.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/defprod1/defprod-skills --skill defprod-onboard-product-defprod1
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: defprod-onboard-product
Source: https://github.com/defprod1/defprod-skills/tree/main/skills/defprod-onboard-product
Command: npx skills add https://github.com/defprod1/defprod-skills --skill defprod-onboard-product-defprod1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning an existing codebase into a structured product definition — brief, areas, user stories, validation, and architecture — is slow and inconsistent when done by hand. This Skill automates that process against the DefProd MCP server, resuming where it left off on each invocation. ## Core Features & Use Cases - Resumable phased onboarding: Checks what already exists in DefProd and starts at the earliest incomplete phase, from product creation through brief, areas, stories, validation, and architecture. - Codebase-grounded user stories: Researches routes, services, data models, and tests to write stories with user-observable acceptance criteria, canonical personas, and a mandatory post-generation lint. - Drift validation: Compares stories and acceptance criteria against the actual implementation and produces a consolidated discrepancy report with fix options. - Use Case: After running repo onboarding, invoke the skill with a product name to generate its brief, propose areas, create user stories per area, validate them against the code, and optionally map the architecture. ## Quick Start Run /defprod-onboard-product with your product name to create or continue its DefProd definition from the current repository.

Frequently Asked Questions about defprod-onboard-product

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I onboard a product into DefProd from an existing codebase?▼

Invoke the skill with the product name after repo onboarding has written docs/defprod-onboarding.md. It checks what already exists in DefProd, then creates or continues the brief, areas, user stories, validation, and optional architecture in phases.

How does the skill generate user stories from code?▼

It researches routes, services, data models, and tests for each area, builds a capability matrix of entities and verbs, then creates stories with user-observable acceptance criteria. A mandatory lint pass fixes implementation leaks, non-canonical personas, and missing write-verb coverage.

Can I resume product onboarding across multiple sessions?▼

Yes. The skill always runs a status check first — listing products, briefs, areas, and stories — and starts at the earliest incomplete phase. Story creation can also be scoped to specific areas per session.

Does defprod-onboard-product work with Cursor or OpenCode?▼

Yes. It is discovered from .claude/skills/ by Claude Code, Cursor, and OpenCode. The body uses logical MCP tool names like listAreas, while the allowed-tools frontmatter is only consumed by Claude Code.

What happens when stories don't match the codebase?▼

Phase 4 runs a discrepancy analysis comparing stories and acceptance criteria against the implementation, then presents a consolidated report across four categories. You can fix all, cherry-pick, or skip the recommended changes.

Why must stories use areaKey instead of areaId?▼

Opaque areaId UUIDs carried in memory across batches drift silently and file stories under the wrong area. The semantic areaKey cannot drift, and the backend cross-checks that each story key starts with the area key.