git:20260817.f7782e4 to git:20260827.e9312a3

---

name: agent-pipeline

description: Defines the 6-stage BDB Software Engineering Pipeline (DEFINE, PLAN, BUILD, VERIFY, REVIEW, SHIP) with corresponding slash commands (/spec, /plan, /build, /test, /review, /ship) and autonomous orchestrator /startcycle.

---

# 🔄 BDB Software Engineering Pipeline

When orchestrating or executing software development, AI agents MUST follow the 6-stage lifecycle pipeline.

```

DEFINE PLAN BUILD VERIFY REVIEW SHIP

┌──────┐ ┌──────┐ ┌──────┐ ┌──────┐ ┌──────┐ ┌──────┐

│ Idea │ ───▶ │ Spec │ ───▶ │ Code │ ───▶ │ Test │ ───▶ │ QA │ ───▶ │ Go │

│Refine│ │ PRD │ │ Impl │ │Debug │ │ Gate │ │ Live │

└──────┘ └──────┘ └──────┘ └──────┘ └──────┘ └──────┘

/spec /plan /build /test /review /ship

└─────────────────────────────────────────────────────────────────────────────┘

🚀 Master Macro: /startcycle

```

---

## ⚡ Autonomous Orchestration: `/startcycle`

To run the entire pipeline autonomously across a multi-agent team without manual step-by-step prompts, invoke:

```bash

/startcycle

```

`/startcycle` automatically assigns:

- **Stages 1 & 2 (DEFINE + PLAN):** `Planner_Orchestrator` ➔ `production_artifacts/00_execution_plan.md`

- **Stage 3 (BUILD):** `Godmode_UI_UX`, `Godmode_Engineering`, `Godmode_Media_EventTech`

- **Stages 4 & 5 (VERIFY + REVIEW):** `Godmode_Shipping` ➔ `production_artifacts/04_release_report.md`

- **Stage 6 (SHIP):** `openwiki-skill` (wiki sync) + `memb-ingest` (vector memory)

---

## 📌 Individual Pipeline Stages & Slash Commands

### 1. DEFINE (`/spec`)

* **Focus:** Idea Refinement & Requirement Elicitation

* **Action:** Interview the user, clarify scope, define key constraints, and gather missing technical docs.

* **Output:** User Stories, Scope Boundaries, and Spec RFCs.

### 2. PLAN (`/plan`)

* **Focus:** Architectural Design & Technical Specification (PRD)

* **Action:** Generate implementation plan artifacts, draw Mermaid diagrams, define file-by-file diffs, and request user approval.

* **Output:** Approved Implementation Plan Artifact (`<plan_name>.md`).

### 3. BUILD (`/build`)

* **Focus:** Code Implementation & Refactoring

* **Action:** Execute plan steps using modular edits, adhere to clean code principles, and avoid breaking existing API contracts.

* **Output:** Functional codebase modifications & newly created components.

### 4. VERIFY (`/test`)

* **Focus:** Automated Testing & Debugging

* **Action:** Run unit test suites, lint checks, and type checkers (`pytest`, `npm test`, `cargo test`, `vitest`). Inspect runtime logs upon failure.

* **Output:** Verified test run outputs (100% green build status).

### 5. REVIEW (`/review`)

* **Focus:** QA Gate & Code Review

* **Action:** Perform architectural reviews, security scans for hardcoded secrets, UI/UX compliance audits (`godmode-ui-ux`), and code simplification passes.

* **Output:** Code review summary & QA gate approval.

### 6. SHIP (`/ship`)

* **Focus:** Production Deployment, Knowledge Sync & Release Gate

* **Action:**

1. **Pre-Push Sanitization (`github-repo`):** Audit for absolute local paths, usernames, and uncommitted secrets.

2. **Codebase Wiki Sync (`openwiki-skill`):** Scan git diff, update `.openwiki/` (`architecture.md`, `release_notes.md`, `quickstart.md`), and refresh `README.md`.

3. **Memory Engine Feeding (`memb-ingest`):** Feed updated docs and architecture into the local memB vector brain (`~/.MemBDB/`) via `memb-mcp` or `memb_ingest.py`.

4. **Release Deployment:** Take git snapshot, commit structured changes, push to private remote repository, and trigger deployment/release tags.

* **Output:** Live deployment confirmation, synced `.openwiki/` release notes, and refreshed memB long-term memory.