skills/development-pipeline/SKILL.md
Complete 9-phase development pipeline guide — from schema to deployment. Pipeline phases (1-schema → 9-deployment) are orthogonal to PDCA's 9-phase per-feature cycle and Sprint's 8-phase container; each pipeline phase may host PDCA cycles for individual features, and multi-feature pipeline initiatives can be wrapped in /sprint (v2.1.13). Triggers: development pipeline, where to start, phase, 개발 파이프라인, 순서, 시작.
npx skillsauth add popup-studio-ai/bkit-claude-code development-pipelineInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Complete knowledge of the 9-phase development pipeline
/pipeline-* commandsThis 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
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
❌ 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 | 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 |
Phase 1 → 2 → 3 → 5(optional) → 6(static) → 7(SEO) → 9
Phase 1 → 2 → 3 → 4(bkend.ai) → 5 → 6 → 7 → 8 → 9
Phase 1 → 2 → 3 → 4(direct impl) → 5 → 6 → 7 → 8 → 9
| 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 |
phase-1-schema/ ~ phase-9-deployment/: Detailed guides per Phasepdca-methodology/: How to apply PDCAstarter/, dynamic/, enterprise/: Level-specific knowledgetesting
Sprint Management — generic sprint capability for ANY bkit user. 16 sub-actions: init, start, status, watch, phase, iterate, qa, report, archive, list, feature, pause, resume, fork, help, master-plan. Triggers: sprint, sprint start, sprint init, sprint status, sprint list, 스프린트, 스프린트 시작, 스프린트 상태, スプリント, スプリント開始, スプリント状態, 冲刺, 冲刺开始, 冲刺状态, sprint, iniciar sprint, estado sprint, sprint, demarrer sprint, statut sprint, Sprint, Sprint starten, Sprint Status, sprint, avviare sprint, stato sprint, master plan, multi-sprint plan, sprint master plan, 마스터 플랜, 멀티 스프린트 계획, 스프린트 마스터 플랜, マスタープラン, マルチスプリント計画, スプリントマスタープラン, 主计划, 多冲刺计划, 冲刺主计划, plan maestro, plan multi-sprint, plan maestro sprint, plan maître, plan multi-sprint, plan maître sprint, Masterplan, Multi-Sprint-Plan, Sprint-Masterplan, piano principale, piano multi-sprint, piano principale sprint.
tools
CC CLI version upgrade impact analysis — research changes, analyze bkit impact, generate report. Triggers: cc-version-analysis, CC upgrade, version analysis, CC 버전 분석, 버전 영향.
testing
Manage PDCA checkpoints and rollback — create, list, restore for safe recovery. Rollback events are recorded via lib/audit/audit-logger ACTION_TYPES.rollback_executed. For sprint-level recovery, individual feature rollbacks may be triggered from within sprint phases (sprint itself is forward-only — terminal state is `archived`, not rolled back; v2.1.13). Triggers: rollback, checkpoint, restore, undo, 롤백, 체크포인트, 복원.
testing
QA Phase execution — L1-L5 test planning, generation, execution, and reporting for a single feature. For sprint-level QA (7-Layer dataFlowIntegrity / S1 gate across multiple features) use /sprint qa <sprintId> which delegates to sprint-qa-flow agent (v2.1.13). Triggers: qa phase, QA test, qa run, QA 실행, QAフェーズ, QA阶段, fase QA, phase QA, QA-Phase, fase QA.