From datum-platform
Covers pipeline orchestration for feature development including stages, handoffs, and artifact management. Use when coordinating work through the discovery to deployment pipeline.
npx claudepluginhub datum-cloud/claude-code-plugins --plugin datum-platformThis skill uses the workspace's default tool permissions.
This skill covers pipeline orchestration for feature development.
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
This skill covers pipeline orchestration for feature development.
Use these commands to orchestrate the pipeline:
| Command | Description |
|---|---|
/pipeline start <name> | Start a new feature pipeline |
/pipeline status <id> | Check current stage and blockers |
/pipeline next <id> | Advance to next stage |
/pipeline list | Show all active pipelines |
/discover <description> | Quick-start feature discovery |
/review [feature-id] | Invoke code review |
/deploy <id> | Trigger deployment workflow |
See commands/ directory for detailed command documentation.
request → discovery → spec → pricing → design → ui-patterns →
implementation → test → review → deploy → document → announce
Some stages can run in parallel:
discovery
├── spec ──────────┐
└── pricing ───────┼── design
│
implementation: │
├── api-dev ───────┤ (parallel)
├── frontend-dev ──┤
└── sre ───────────┘
│
post-deploy: │
├── document ──────┤ (parallel)
└── announce ──────┘
| Input Type | Starting Stage |
|---|---|
| Feature idea | discovery |
| Clear requirements | spec |
| Bug fix | implementation |
| Doc update | document |
| Hotfix | implementation → deploy |
Approval required after:
Approve with: /pipeline approve <id> <gate>
All artifacts live in .claude/pipeline/:
.claude/pipeline/
├── requests/ # Feature requests
├── briefs/ # Discovery briefs
├── specs/ # Specifications
├── pricing/ # Pricing briefs
├── designs/ # Architecture designs
├── ui-patterns/ # UI specifications
├── triage/ # Support triage docs
└── comms/ # GTM content
Pattern: {id}-{name}.md
Example: feat-001-vm-snapshots.md
Each agent reads upstream artifacts and writes downstream:
| Agent | Reads | Writes |
|---|---|---|
| product-discovery | requests/ | briefs/ |
| product-planner | briefs/ | specs/ |
| commercial-strategist | briefs/, specs/ | pricing/ |
| architect | specs/, pricing/ | designs/ |
| api-dev | designs/ | code |
| code-reviewer | designs/, code | findings |
All pipeline artifacts MUST include structured handoff headers. See handoff-format.md for the complete schema.
Key fields:
context_summary: What this artifact representsdecisions_made: Key decisions with rationaleopen_questions: Unresolved items (blocking vs non-blocking)assumptions: What was assumed, with confidence levelsplatform_capabilities: Quota, insights, telemetry, activity decisionsSee templates/ for stage-specific templates with handoff headers:
templates/discovery-brief.md - Discovery phase outputtemplates/spec.md - Specification documenttemplates/pricing-brief.md - Commercial strategy outputtemplates/design.md - Architecture design documentRequired sections:
Required sections:
Required sections: