development-pipeline

9-phase Development Pipeline complete knowledge. Use when user doesn't know development order or starts a new project from scratch. Use proactively when user asks about development order, phases, what to do first, or starts a new project without clear direction. Triggers: development pipeline, phase, development order, where to start, what to do first, how to begin, new project, 개발 파이프라인, 뭐부터, 어디서부터, 순서, 시작, 開発パイプライン, 何から, どこから, 开发流程, 从哪里开始, pipeline de desarrollo, fase, orden de desarrollo, por dónde empezar, qué hacer primero, pipeline de développement, phase, ordre de développement, par où commencer, que faire d'abord, Entwicklungspipeline, Phase, Entwicklungsreihenfolge, wo anfangen, was zuerst tun, pipeline di sviluppo, fase, ordine di sviluppo, da dove iniziare, cosa fare prima Do NOT use for: ongoing implementation, existing feature work, or bug fixes.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "development-pipeline" with this command: npx skills add popup-studio-ai/bkit-claude-code/popup-studio-ai-bkit-claude-code-development-pipeline

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

PhaseStarterDynamicEnterprise
1. Schema/TermsSimpleDetailedDetailed
2. ConventionBasicExtendedExtended
3. MockupOOO
4. API-bkend.aiDirect impl
5. Design SystemOptionalOO
6. UI + APIStatic UIIntegrationIntegration
7. SEO/SecuritySEO onlyOO
8. Review-OO
9. DeploymentStatic hostingVercel 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

PhaseKey Deliverables
1docs/01-plan/schema.md, terminology.md
2CONVENTIONS.md, docs/01-plan/naming.md
3mockup/ folder, docs/02-design/mockup-spec.md
4docs/02-design/api-spec.md, src/api/
5components/ui/, docs/02-design/design-system.md
6src/pages/, src/features/
7docs/02-design/seo-spec.md, security-spec.md
8docs/03-analysis/architecture-review.md
9docs/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

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Coding

desktop-app

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

mobile-app

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

phase-3-mockup

No summary provided by upstream source.

Repository SourceNeeds Review