agentleFS
Sign inStart free
popup-studio-aipopup-studio-ai/bkit-claude-code/skills/development-pipeline/SKILL.md

development-pipeline

Skill605 starsChanged 3 months agoApache-2.0View on GitHub

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

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When user says "I have little development experience"

    line 26
  2. Very specific:

    When using /pipeline-* commands

    line 27
  3. Distinctive:

    When asked "How do I start development?", "What's the order?"

    line 28
  4. Distinctive:

    When starting a new project from scratch

    line 29

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free