ai-prose
$
npx mdskill add arcasilesgroup/ai-engineering/ai-prose``` /ai-prose content blog /ai-prose content sprint-review --audience manager /ai-prose content architecture-board ```
SKILL.md
.github/skills/ai-proseView on GitHub ↗
---
name: ai-prose
description: Writes content (blog posts, pitch decks, sprint review summaries, architecture board reports, solution intent documents) with automatic audience targeting (developer/manager/executive). Trigger for 'write a blog post', 'pitch this', 'sprint review summary', 'architecture board doc', 'solution intent for'. Not for documentation artifacts like CHANGELOG or README; use /ai-docs instead. Not for marketing/social content; use /ai-marketing instead. Not for code-level explanations; use /ai-explain instead.
effort: mid
argument-hint: "content [type] [--audience developer|manager|executive]"
mode: agent
tags: [writing, content, communication]
model_tier: sonnet
mirror_family: copilot-skills
generated_by: ai-eng sync
canonical_source: .claude/skills/ai-prose/SKILL.md
edit_policy: generated-do-not-edit
---
# Prose
## Quick start
```
/ai-prose content blog
/ai-prose content sprint-review --audience manager
/ai-prose content architecture-board
```
## Workflow
1. Detect content type from prompt (blog / pitch / sprint-review / architecture-board / solution-intent / presentation).
2. Read existing source material — notes, transcripts, data, real output.
3. Pick audience (developer / manager / executive); apply tone + jargon table.
4. Edit, do not generate. Every sentence earns its place.
5. Apply shared rules: active voice, present tense, no filler ("basically", "simply", "just").
Router skill for content writing. Dispatches to handler files based on content type. Always: clear structure, audience-appropriate, no fluff.
## When to Use
- Creating pitch decks, sprint reviews, blog posts, architecture board presentations, solution intent documents.
- NOT for documentation artifacts (README, CHANGELOG, API docs) -- use `/ai-docs`.
- NOT for marketing content (social posts, investor materials, outreach) -- use `/ai-marketing`.
- NOT for code explanations -- use `/ai-explain`.
## Writing Philosophy
Edit, don't generate. Start from what exists: notes, transcripts, data, examples, real output. Every sentence must earn its place. Template language is a failure mode, not a starting point.
## Routing
Single sub-command `content` (default) — handler `handlers/content.md` covers articles, pitches, presentations, sprint reviews, architecture board, solution intent. The handler dispatches to sub-types internally based on the content type in the user's prompt.
## Audience Targeting
| Audience | Tone | Detail Level | Jargon |
|----------|------|-------------|--------|
| `developer` | Technical, precise | Implementation details | Full technical vocabulary |
| `manager` | Results-oriented | Impact and timeline | Minimal, explained when used |
| `executive` | Strategic | Business value and risk | None |
Default: `developer`.
## Quick Reference
```
/ai-prose content pitch # elevator pitch
/ai-prose content sprint-review # sprint review summary
/ai-prose content blog # blog post
/ai-prose content presentation # presentation outline
/ai-prose content architecture-board # architecture decision for review
/ai-prose content solution-intent # solution intent document
/ai-prose content blog --audience manager # manager-targeted blog post
```
## Shared Rules
- Write what users can DO, not what you BUILT.
- Active voice. Present tense.
- No "basically", "simply", "just".
- Every section earns its place -- cut anything that does not serve the reader.
- Audience determines vocabulary, not quality.
## Examples
### Example 1 — sprint review for a manager audience
User: "write the sprint review summary for this week"
```
/ai-prose content sprint-review --audience manager
```
Reads recent commits + closed issues, generates a results-oriented summary with impact + timeline framing, omits implementation jargon.
### Example 2 — pitch deck for executive review
User: "draft an elevator pitch for the new auth product"
```
/ai-prose content pitch --audience executive
```
Strategic framing, business value first, no technical vocabulary, ≤90 words.
## Integration
Called by: user directly. Dispatches to: `handlers/content.md`. See also: `/ai-docs` (CHANGELOG/README), `/ai-marketing` (social/outreach), `/ai-explain` (code-level), `/ai-slides` (deck rendering).
$ARGUMENTS
More from arcasilesgroup/ai-engineering
- ai-adviseProactive governance advisor — checks standards, decisions, and quality trends during development. Always advisory, NEVER blocks. Three modes: `advise` (post-edit), `gate` (pre-dispatch), `drift` (on-demand decision audit). Trigger for 'governance check', 'advise on this change', 'check for drift', 'is this aligned with active decisions', 'shift-left advisory'. Not for blocking gates — use /ai-verify. Not for narrative code review — use /ai-review.
- ai-analyze-permissionsUse when Claude Code keeps asking to approve commands you have already approved, when settings.local.json has grown large, or when you want to consolidate permission grants into wildcard patterns. Trigger for 'too many permission prompts', 'clean up permissions', 'audit my settings', 'consolidate allow rules'. Claude Code only — not available in GitHub Copilot, Antigravity, or Codex.
- ai-animationDesigns motion, transitions, and micro-interactions for UI components: spring animations, gestures, easing, staggers — taste-driven detail compounding. Trigger for 'animate this', 'add transitions', 'micro-interactions for', 'gesture design', 'swipe to dismiss', 'easing for this', 'stagger the'. Not for design systems; use /ai-design instead. Not for visual art; use /ai-visual instead. Not for testing animation code; use /ai-test instead.
- ai-autopilotDelivers large multi-concern specs and backlog runs autonomously: decomposes specs into sub-specs (or normalizes work items into a backlog DAG), deep-plans with parallel agents, builds a dependency DAG, implements in waves, runs a single final quality loop with one bounded quality-remediation pass (verify+guard+review on full changeset), delivers via PR. Trigger for 'implement spec-NNN end to end', 'autopilot this', 'autonomous delivery', 'decompose and ship', 'run the backlog', 'execute these GitHub issues', 'process the sprint backlog'. Invocation is the approval gate. Not for small or single-concern tasks; use /ai-build instead. Not for ambiguous requirements; use /ai-brainstorm first.
- ai-boardOperates the project board (GitHub Projects v2 or Azure DevOps): discovers configuration after install (fields, state mappings, process templates) and syncs work-item state at lifecycle transitions. Trigger for 'set up the board', 'configure our ADO board', 'discover board fields', 'move this issue to in-review', 'update the board', 'mark as in progress', 'sync the work item state'. Two subcommands: `discover` (post-install configuration write) and `sync` (lifecycle state transitions). Auto-invoked via `sync` by /ai-brainstorm, /ai-build, and /ai-pr; fail-open. Not for backlog execution; use /ai-autopilot --backlog instead.
- ai-brainstormForces rigorous design interrogation BEFORE any code: explores approaches, surfaces ambiguity, gathers evidence, produces an approved spec that becomes the contract for /ai-plan. Trigger for 'lets add X', 'how should we handle Y', 'whats the best approach', 'I am thinking about', 'what should we build for'. Not for existing approved specs; use /ai-plan instead. Not for execution; use /ai-build instead.
- ai-branch-cleanupCleans branches safely: switches to the default branch, prunes merged and squash-merged branches, syncs to remote, sweeps stale specs, rotates `.ai-engineering/runtime/` per retention policy. Trigger for 'tidy up', 'tidy branches', 'sync to main', 'delete old branches', 'start fresh', 'rotate runtime'. Auto-invoked by /ai-pr after merge. Not for committing changes; use /ai-commit instead. Not for code-level dead-code removal; use /ai-simplify instead.
- ai-buildCanonical implementation gateway: reads approved plan.md, resolves stack from manifest, deterministic-routes each task to its adapter, dispatches the build agent in an isolated worktree, runs TDD self-validation per task, then a single final quality loop with one bounded quality-remediation pass on the full changeset before /ai-pr. Trigger for 'go', 'start building', 'execute the plan', 'implement it', 'lets do this', 'build the plan', 'resume', 'continue'. Not without an approved plan; run /ai-plan first. Not for multi-concern specs needing decomposition; use /ai-autopilot instead. Not for a single function or subcomponent; use /ai-code.
- ai-codeWrites production code that satisfies stack-context standards on the first pass: interface-first design, backward-compatibility checks, lightweight self-review. Trigger for 'implement this', 'write the code for', 'add X to Y', 'build this function', 'make this work'. Not for tests; use /ai-test instead. Not for debugging; use /ai-debug instead. Not for refactoring; use /ai-simplify instead. Not for executing an approved plan end-to-end; use /ai-build (the gateway).
- ai-commitRuns the governed commit pipeline: auto-branches from protected, stages selectively, formats and lints, scans for secrets, gates docs, composes a conventional message, pushes. Trigger for 'commit my changes', 'save my work', 'push this to remote', 'stage these files', 'ship it'. Not for opening a PR; use /ai-pr instead. Not for branch hygiene; use /ai-branch-cleanup instead.