🎯

development-pipeline

🎯Skill

from popup-studio-ai/bkit-claude-code

VibeIndex|
What it does

Guides developers through a comprehensive 9-phase development pipeline, providing structured roadmap for new project creation and systematic software development.

πŸ“¦

Part of

popup-studio-ai/bkit-claude-code(17 items)

development-pipeline

Installation

Add MarketplaceAdd marketplace to Claude Code
/plugin marketplace add popup-studio-ai/bkit-claude-code
Install PluginInstall plugin from marketplace
/plugin install bkit
πŸ“– Extracted from docs: popup-studio-ai/bkit-claude-code
3Installs
-
AddedFeb 4, 2026

Skill Details

SKILL.md

|

Overview

# Development Pipeline Skill

> Complete knowledge of the 9-phase development pipeline

When to Use

  • When user says "I have little development experience"
  • When using /pipeline-* commands
  • When asked "How do I start development?", "What's the order?"
  • When starting a new project from scratch

Optional Application Principle

```

This skill is optional, not mandatory.

Activation conditions:

  • When non-developers/beginner developers start development
  • When user explicitly requests guidance
  • When /pipeline-start command is used

Deactivation conditions:

  • When experienced developers want to "proceed freely"
  • For non-development AI work (documentation, analysis, etc.)
  • For existing project maintenance/bug fixes

```

9-Phase Pipeline Overview

```

Phase 1: Schema/Terminology ──→ Define data structures and domain terms

Phase 2: Coding Convention ────→ Define code writing rules

Phase 3: Mockup Development ───→ Feature validation with HTML/CSS/JS + JSON

Phase 4: API Design/Impl ──────→ Backend API + Zero Script QA

Phase 5: Design System ────────→ Build component system

Phase 6: UI Implementation ────→ Actual UI implementation and API integration

Phase 7: SEO/Security ─────────→ Search optimization and security hardening

Phase 8: Review ───────────────→ Architecture/convention quality verification

Phase 9: Deployment ───────────→ Production deployment

```

Relationship with PDCA (Key Concept)

```

❌ Wrong understanding: Mapping entire Pipeline to PDCA

❌ (Plan=Phase1-3, Do=Phase4-6, Check=Phase7-8, Act=Phase9)

βœ… Correct understanding: Run PDCA cycle within each Phase

Phase N

β”œβ”€β”€ Plan: Plan what to do in this Phase

β”œβ”€β”€ Design: Detailed design

β”œβ”€β”€ Do: Execute/implement

β”œβ”€β”€ Check: Verify/review

└── Act: Confirm and move to next Phase

```

Phase Application by Level

| Phase | Starter | Dynamic | Enterprise |

|-------|---------|---------|------------|

| 1. Schema/Terms | Simple | Detailed | Detailed |

| 2. Convention | Basic | Extended | Extended |

| 3. Mockup | O | O | O |

| 4. API | - | bkend.ai | Direct impl |

| 5. Design System | Optional | O | O |

| 6. UI + API | Static UI | Integration | Integration |

| 7. SEO/Security | SEO only | O | O |

| 8. Review | - | O | O |

| 9. Deployment | Static hosting | Vercel etc. | K8s |

Starter Level Flow

```

Phase 1 β†’ 2 β†’ 3 β†’ 5(optional) β†’ 6(static) β†’ 7(SEO) β†’ 9

```

Dynamic Level Flow

```

Phase 1 β†’ 2 β†’ 3 β†’ 4(bkend.ai) β†’ 5 β†’ 6 β†’ 7 β†’ 8 β†’ 9

```

Enterprise Level Flow

```

Phase 1 β†’ 2 β†’ 3 β†’ 4(direct impl) β†’ 5 β†’ 6 β†’ 7 β†’ 8 β†’ 9

```

Phase Deliverables Summary

| Phase | Key Deliverables |

|-------|-----------------|

| 1 | docs/01-plan/schema.md, terminology.md |

| 2 | CONVENTIONS.md, docs/01-plan/naming.md |

| 3 | mockup/ folder, docs/02-design/mockup-spec.md |

| 4 | docs/02-design/api-spec.md, src/api/ |

| 5 | components/ui/, docs/02-design/design-system.md |

| 6 | src/pages/, src/features/ |

| 7 | docs/02-design/seo-spec.md, security-spec.md |

| 8 | docs/03-analysis/architecture-review.md |

| 9 | docs/04-report/deployment-report.md |

Related Skills

  • phase-1-schema/ ~ phase-9-deployment/: Detailed guides per Phase
  • pdca-methodology/: How to apply PDCA
  • starter/, dynamic/, enterprise/: Level-specific knowledge