development-pipeline
9-phase Development Pipeline complete knowledge. Use when user doesn't know development order or starts a new project. Triggers: development pipeline, phase, development order, where to start, what to do first, how to begin, new project, 개발 파이프라인, 뭐부터, 어디서부터, 순서, 시작, 開発パイプライン, 何から, どこから, 开发流程, 从哪里开始, pipeline de desarrollo, por dónde empezar, pipeline de développement, par où commencer, Entwicklungs-Pipeline, wo anfangen, pipeline di sviluppo, da dove iniziare Do NOT use for: ongoing implementation, bug fixes
Source facts
- Repository
- ww-w-ai/bkit-gemini
- Last source activity
- March 11, 2026 at 04:41
- Detected SKILL.md language
- English
- Stars
- 66
- Forks
- 16
Install options
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Review the source files
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Showing SKILL.md
SKILL.md
Source instructions · Read-only preview- name
- development-pipeline
- classification
- W
- description
- 9-phase Development Pipeline complete knowledge. Use when user doesn't know development order or starts a new project. Triggers: development pipeline, phase, development order, where to start, what to do first, how to begin, new project, 개발 파이프라인, 뭐부터, 어디서부터, 순서, 시작, 開発パイプライン, 何から, どこから, 开发流程, 从哪里开始, pipeline de desarrollo, por dónde empezar, pipeline de développement, par où commencer, Entwicklungs-Pipeline, wo anfangen, pipeline di sviluppo, da dove iniziare Do NOT use for: ongoing implementation, bug fixes
- user-invocable
- true
- argument-hint
- [start|next|status]
- allowed-tools
- ["read_file","glob","grep_search","write_file","tracker_list_tasks","tracker_visualize"]
- imports
- []
- agents
- {"guide":"pipeline-guide"}
- context
- session
- memory
- user
- pdca-phase
- all
# Development Pipeline
> 9-Phase Development Pipeline for systematic project development
## The 9 Phases
| Phase | Name | Purpose | PDCA |
|-------|------|---------|------|
| 1 | Schema | Define terminology & data structures | Plan |
| 2 | Convention | Set coding rules & standards | Plan |
| 3 | Mockup | Create UI/UX prototypes | Design |
| 4 | API | Design & implement backend API | Do |
| 5 | Design System | Build component library | Do |
| 6 | UI Integration | Connect frontend to backend | Do |
| 7 | SEO/Security | Optimize & secure | Do |
| 8 | Review | Code & architecture review | Check |
| 9 | Deployment | Deploy to production | Act |
## Phase by Level
### Starter (Static Web)
```
Phase 1 → 2 → 3 → 6 → 9
(Skip: 4, 5, 7, 8)
```
### Dynamic (Fullstack)
```
Phase 1 → 2 → 3 → 4 → 6 → 9
(Optional: 5, 7, 8)
```
### Enterprise (Microservices)
```
Phase 1 → 2 → 3 → 4 → 5 → 6 → 7 → 8 → 9
(All required)
```
## Commands
```bash
# Start pipeline
/development-pipeline start
# Check current status
/development-pipeline status
# Move to next phase
/development-pipeline next
```
## Phase Details
### Phase 1: Schema
- Define domain terminology
- Create data models
- Document relationships
### Phase 2: Convention
- Naming conventions
- Code style rules
- Git workflow
### Phase 3: Mockup
- Wireframes
- UI components
- User flows
### Phase 4: API
- Endpoint design
- Request/response schemas
- Authentication
### Phase 5: Design System
- Component library
- Design tokens
- Storybook
### Phase 6: UI Integration
- Frontend implementation
- State management
- API integration
### Phase 7: SEO/Security
- Meta tags
- Security headers
- Vulnerability scan
### Phase 8: Review
- Code review
- Architecture audit
- Performance check
### Phase 9: Deployment
- CI/CD setup
- Environment config
- Go live
View on GitHub