Full development pipeline: create GitHub issue, plan, implement with agent team, verify (build+test), commit, push, close issue. Use when you need to implement a feature or fix end-to-end.
Scanned 8/31/2026
Install via CLI
openskills install spytensor/openmozi---
name: pipeline
description: "Full development pipeline: create GitHub issue, plan, implement with agent team, verify (build+test), commit, push, close issue. Use when you need to implement a feature or fix end-to-end."
disable-model-invocation: true
---
# Development Pipeline
Automate the full development lifecycle for a feature or fix described by `$ARGUMENTS`.
## Workflow
Execute these steps in order. Stop and report if any step fails.
### Step 1: Create GitHub Issue
```bash
gh issue create --title "<concise title from $ARGUMENTS>" --body "<detailed description>"
```
Parse the returned URL to extract the issue number. Print it.
### Step 2: Plan
- Research the codebase to understand what files need changing
- Design the implementation approach
- Identify all files to modify/create
- Write the plan to a file at `.claude/plans/<issue-number>.md`
### Step 3: Build Agent Team & Implement
- Use `TeamCreate` to create a team named after the issue
- Break the plan into independent tasks using `TaskCreate`
- Spawn agents in parallel using the `Task` tool with `team_name` parameter:
- Each agent handles one task (one file or one concern)
- Use `subagent_type: "general-purpose"` with `mode: "bypassPermissions"`
- Run agents in background when possible
- Wait for all agents to complete by checking `TaskList`
### Step 4: Review
- Read the modified files to verify changes are correct
- Check for obvious issues, missing imports, type errors
### Step 5: Verify
Run build and tests:
```bash
pnpm build
pnpm test
```
If build or tests fail:
1. Read the error output
2. Fix the issues directly
3. Re-run verification
4. Repeat until passing
### Step 6: Commit & Push
```bash
git add <changed files>
git commit -m "feat: <description> (#<issue-number>)
Co-authored-by: Mozi <MoziAI-co@users.noreply.github.com>"
git push origin main
```
### Step 7: Close Issue
```bash
gh issue close <issue-number> --comment "Implemented in <commit-hash>."
```
### Step 8: Cleanup
- Shut down all team agents via `SendMessage` with `type: "shutdown_request"`
- Delete the team via `TeamDelete`
- Report final summary: issue number, commit hash, files changed, test results
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.