agentleFS
ww-w-aiww-w-ai/bkit-codex/.agents/skills/development-pipeline/SKILL.md

development-pipeline

Skill69 starsChanged 8 months agoApache-2.0View on GitHub

9-phase Development Pipeline overview. Use when starting a new project or unsure about development order. Triggers: development pipeline, phase, development order, where to start, 개발 파이프라인, 뭐부터, 어디서부터, 開発パイプライン, 何から, 开发流程, 从哪里开始, pipeline de desarrollo, pipeline de développement Do NOT use for: specific phase details (use $phase-N-xxx).

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Design: Create detailed specifications

    line 91
  2. Very specific:

    Use $pdca skill for PDCA workflow management within each phase.

    line 94
  3. Distinctive:

    Follow the pipeline for your level

    line 99
  4. Very specific:

    Use $phase-N-xxx skills for detailed guidance in each phase

    line 100

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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

9-phase Development Pipeline overview and navigation guide.

Actions

ActionDescriptionExample
overviewShow all 9 phases$development-pipeline overview
recommendRecommend pipeline for level$development-pipeline recommend starter
statusCheck current phase progress$development-pipeline status

The 9 Phases

PhaseNameSkillPurpose
1Schema$phase-1-schemaData modeling, terminology definition
2Convention$phase-2-conventionCoding standards, naming rules
3Mockup$phase-3-mockupUI/UX wireframes, screen design
4API$phase-4-apiAPI design, REST endpoints
5Design System$phase-5-design-systemComponent library, design tokens
6UI Integration$phase-6-ui-integrationFrontend-backend connection
7SEO & Security$phase-7-seo-securitySEO optimization, security hardening
8Review$phase-8-reviewCode review, architecture review
9Deployment$phase-9-deploymentCI/CD, production deployment

Pipeline by Level

Starter (Beginner)

Phase 1 -> 2 -> 3 -> 6 -> 9
  • Skip: Phase 4 (no API), Phase 5 (optional), Phase 7 (basic SEO only), Phase 8 (simple review)
  • Focus: Get a static site live quickly
  • Time: 1-3 days

Dynamic (Intermediate)

Phase 1 -> 2 -> 3 -> 4 -> 5 -> 6 -> 7 -> 9
  • Skip: Phase 8 (simplified review integrated into Phase 7)
  • Focus: Fullstack app with BaaS backend
  • Time: 3-7 days

Enterprise (Advanced)

Phase 1 -> 2 -> 3 -> 4 -> 5 -> 6 -> 7 -> 8 -> 9
  • All 9 phases required
  • Each phase uses PDCA cycle
  • Focus: Production-grade scalable systems
  • Time: 7-14 days (AI Native 10-Day pattern)

Phase Dependencies

Phase 1 (Schema)
  └── Phase 2 (Convention) - needs terminology from Phase 1
        └── Phase 3 (Mockup) - needs naming rules from Phase 2
              ├── Phase 4 (API) - needs UI understanding from Phase 3
              │     └── Phase 5 (Design System) - needs API contracts from Phase 4
              │           └── Phase 6 (UI Integration) - needs components + API
              │                 └── Phase 7 (SEO & Security) - needs working app
              │                       └── Phase 8 (Review) - needs complete app
              │                             └── Phase 9 (Deployment) - needs reviewed code
              └── Phase 6 (Starter shortcut) - static sites skip API/Design System

PDCA Integration

Each phase follows the PDCA cycle:

  1. Plan: Define goals and deliverables for the phase
  2. Design: Create detailed specifications
  3. Check/Act: Review output, iterate if needed

Use $pdca skill for PDCA workflow management within each phase.

How to Start

  1. Determine your project level: $starter, $dynamic, or $enterprise
  2. Follow the pipeline for your level
  3. Use $phase-N-xxx skills for detailed guidance in each phase
  4. Track progress with $pdca status

Common Questions

QuestionAnswer
Can I skip phases?Yes, for Starter/Dynamic levels. See pipeline above.
Can I go back to a previous phase?Yes, PDCA allows iteration. Update docs accordingly.
Which phase am I in?Run $pdca status or check .pdca-status.json
Do I need all phases for MVP?Starter pipeline (5 phases) is sufficient for MVP.

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.

Reviews can't be read right now.

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.