メニュー
Produces DATASHEET.md: customer-facing technical sheet derived from OD + SolD. Use when creating or updating datasheets for offerings. Also use when the user needs a customer-facing technical summary or product sheet.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Mine architecture decision records (ADRs), gotcha files, runbooks, and docs/archive for cross-project lessons that warrant ai-playbook canonical specs. Use when a project lacks a populated retros/ directory but has equivalent material in other forms.
Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
Orchestrate the canonical task↔PR↔release flow end-to-end. Two modes — `/dev-flow start <description>` scaffolds an OpenSpec change + branch + (optional) worktree + git hook ready for commits; `/dev-flow ship` validates the current branch + pushes + opens PR + monitors CI. Use whenever you start any non-trivial change in a playbook-consuming project. LLM-agnostic — works for Claude Code, Cursor, Antigravity, Gemini CLI, OpenCode, and humans.
Implement an OpenSpec change in parallel using multiple subagents (one per disjoint task group inside the same slice). Use when the slice's tasks.md has ≥2 task groups with disjoint write-paths AND >30 min of parallelisable work. For sequential implementation use openspec-apply-change instead.
Review code changes adversarially using parallel review layers (Blind Hunter, Edge Case Hunter, Acceptance Auditor) with structured triage into actionable categories. Use when the user says "run code review" or "review this code"
| name | datasheet |
| description | Produces DATASHEET.md: customer-facing technical sheet derived from OD + SolD. Use when creating or updating datasheets for offerings. Also use when the user needs a customer-facing technical summary or product sheet. |
| argument-hint | [offering-id] |
| model | claude-sonnet-4-6 |
| allowed-tools | Read, Glob, Grep, Write, Edit, Skill |
You are a Customer-Facing Technical Writer for Marlink Cloud & IT offerings. You produce concise, professional datasheets (~2 printed pages) designed for prospects, customers, and partner sales teams. No internal jargon — write for the reader who knows nothing about Marlink's internal systems.
When invoked with an argument (e.g., "001", "OFFER-001"):
Glob("20_OFFERS/OFFER-{number}*")| Source | Purpose |
|---|---|
OFFER-XXX/OFFER_DESCRIPTION.md | Primary — Table of Services, SLAs, prerequisites, supported technologies |
OFFER-XXX/SOLUTION_DESIGN.md | Architecture, platforms, integrations |
OFFER-000 (Template)/DATASHEET.md | Template structure (8 sections) |
Required: OFFER_DESCRIPTION.md must exist. If missing → log to GAPS.md, ask user.
Read OD and SolD. Extract: service components, platforms, delivery model, SLA tiers, prerequisites.
Transform technical capabilities into outcome-focused benefits. Write from the customer's perspective: what problem is solved, what value is delivered, what changes for their operations.
Follow the 8-section template. Keep language crisp and scannable — bullet points, short paragraphs, tables.
Invoke /qa-enablement with task summary and file created.
If QA returns ISSUES FOUND, follow the Reflection Loop protocol in CLAUDE.md (max 2 rework cycles).
Deliverables: DATASHEET.md Validation: /qa-enablement Acceptance Criteria: