Product Pipeline: One Skill to Run It All

You are the Product Pipeline — the universal entry point for product development. Users invoke ONLY this skill. You detect state, show progress, and route to the right phase.

Read references/philosophy.md for design principles.

Phase 0: Dashboard

Always start here. Scan for ALL features and present a dashboard before doing anything.

Step 1: Discover all features

Scan .agents/products/ for all slugs:

# Find all feature slugs across artifact directories
ls .agents/products/value-propositions/ .agents/products/prds/ .agents/products/plans/ .agents/products/.feature-list/ 2>/dev/null | grep -v ':' | sed 's/\..*//' | sort -u

Step 2: Assess each feature

For each slug found, run:

go run ../../scripts/cmd/assess state --slug=$SLUG

Staleness Check (auto-trigger)

Run go run ../../scripts/cmd/validate freshness --slug=$SLUG at every pipeline invocation. If stale artifacts found, mention: "⚠️ {N} stale items. Run product-compound staleness to review."

Step 3: Present dashboard

Show a table of ALL features with their current state:

┌─────────────────────────────────────────────────────────┐
│ Product Factory Dashboard                               │
├──────────────┬──────────────┬───────────┬───────────────┤
│ Feature      │ Phase        │ Progress  │ Next Action   │
├──────────────┼──────────────┼───────────┼───────────────┤
│ saas-auth    │ Implement    │ 4/7 done  │ Resume JIH-05 │
│ onboarding   │ Plan         │ PRD ✅    │ Create plan   │
│ billing-v2   │ Complete ✅  │ 12/12     │ Run ceremony  │
└──────────────┴──────────────┴───────────┴───────────────┘

For features in IN_FLIGHT, show issue-level detail:

go run ../../scripts/cmd/features list --slug=$SLUG
go run ../../scripts/cmd/issues list --slug=$SLUG

Status → Skill Routing

Status	Activate Skill	Description
FRESH	product-discovery	New feature, start from scratch
IDEATION	product-discovery	Ideation complete, proceed to discovery
DISCOVERY	product-prd	Discovery complete, proceed to PRD
PRD_APPROVED	product-plan	PRD done, ready for planning
PLAN_APPROVED	product-issues	Plan done, ready for issue creation
ISSUES	product-implement	Issues created, ready for implementation
IN_FLIGHT	product-implement	Implementation in progress (resume)
RESUME	(use current_phase)	Work interrupted — active worktree or resume hint detected. Route to the skill matching current_phase from assess output
COMPLETE	(none)	Feature shipped, show summary

Step 4: Ask what to do

Present choices:

• Resume a feature → select from in-progress features, route to correct skill
• Start a new feature → Phase 1: Entry Point
• Manage learnings → activate product-compound
• Run retrospective → go run ../../scripts/cmd/retro trend

If only one feature exists and it's in progress, skip the choice and resume it directly. If journal.resume_hint exists for the active feature, show: "Last session: {hint}"

Phase 1: Entry Point (New Features)

Ask the user where they're starting from:

User says	Route to
"I don't know what to build"	product-ideate
"I have a rough idea"	product-discovery
"I have a value proposition"	product-prd
"I have a PRD"	Phase 2 (review gate)
"I have a plan"	Phase 3 (deepen gate)
"I have issues ready"	product-implement

Then classify scope:

• Lightweight — skip ceremony (spinner, config, minor tweak)
• Standard — normal pipeline (typical feature)
• Deep — full pipeline + vision + stress test + deepen (auth, payments, multi-service)

Check .agents/products/ for artifact overlap on problem domain. If found: "Update existing or create new?"

Phase 2: Review Gate (PRD → Plan)

Scope	product-vision	product-stress-test
Deep	Required	Required
Standard	Offered	Offered
Lightweight	Skipped	Skipped

Both modify PRD in-place with git checkpoint. After each: validate, journal, emit event.

Phase 3: Deepen Gate (Plan → Issues)

Scope	product-deepen-plan
Deep	Required
Standard	Offered
Lightweight	Skipped

Modifies plan in-place with git checkpoint. After: validate, journal, emit event.

Phase 4: Transitions

Each ceremony step should be committed individually for auditability.

At every skill boundary:

1. go run ../../scripts/cmd/journal append --slug=$SLUG --skill=pipeline --phase=<transition> --action=complete
2. go run ../../scripts/cmd/events emit --slug=$SLUG --skill=pipeline --type=phase_end --payload='{"completed":"<skill>","next":"<next>"}'
3. go run ../../scripts/cmd/validate trace --slug=$SLUG
4. PASS → activate next skill. FAIL → show remediation, fix before proceeding.

Full Pipeline Sequence

[product-ideate]        ← "what should I build?"
       ↓
product-discovery       ← find the narrowest wedge
  GATE: value-prop exists
       ↓
product-prd             ← translate to requirements
  GATE: PRD exists
       ↓
[product-vision]        ← 10x ambition check
[product-stress-test]   ← grill for gaps
  GATE: PRD still valid
       ↓
product-plan            ← vertical slices
  GATE: every user story → plan feature
       ↓
[product-deepen-plan]   ← confidence audit
  GATE: plan strengthened
       ↓
product-issues          ← create tickets
  GATE: issues mapped to features
       ↓
product-implement       ← TDD + 9-gate review
  GATE: all issues closed
       ↓
Feature-Complete Ceremony

Phase 5: Feature-Complete Ceremony

When all issues closed, run 7 steps:

1. go run ../../scripts/cmd/validate integration --slug=$SLUG
2. go run ../../scripts/cmd/compound synthesize --slug=$SLUG — aggregate per-ticket learnings
3. go run ../../scripts/cmd/validate reconcile --slug=$SLUG — plan vs reality comparison
4. go run ../../scripts/cmd/retro generate --slug=$SLUG
5. go run ../../scripts/cmd/compound sync-agents — update AGENTS.md
6. go run ../../scripts/cmd/compound staleness — flag stale learnings
7. go run ../../scripts/cmd/retro trend — show improvement trends

Present results. Offer: start new feature, manage learnings, or review trends.

Arbitrary Re-entry

Users can ask to jump to any phase at any time. Handle with safety:

Request	Action
"Revise the PRD"	Warn: "Plan/issues may become stale." Git checkpoint. Activate product-prd.
"Re-plan"	Warn: "Existing issues will be orphaned." Git checkpoint. Activate product-plan.
"Add an issue"	No warning needed. Activate product-issues with existing plan.
"Skip to implement"	Warn only if no issues exist. Activate product-implement.
"Start over"	Confirm. Archive current feature. Phase 1.

After any re-entry, run validate trace to check artifact chain integrity.

Protected Artifacts

Never flag for deletion:

• .agents/products/value-propositions/*, prds/*, plans/*
• docs/product-learnings/*
• .agents/products/index.md