skill-deck-implement
Route deck implementation to deck-builder-agent for Slidev pitch deck generation
Best use case
skill-deck-implement is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Route deck implementation to deck-builder-agent for Slidev pitch deck generation
Teams using skill-deck-implement should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/skill-deck-implement/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How skill-deck-implement Compares
| Feature / Agent | skill-deck-implement | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Route deck implementation to deck-builder-agent for Slidev pitch deck generation
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Deck Implement Skill
Routes deck-specific implementation requests to the `deck-builder-agent`, generating Slidev pitch decks from plans created by `skill-deck-plan` and research from `skill-deck-research`.
## Context Pointers
Reference (do not load eagerly):
- Path: `.claude/context/formats/subagent-return.md`
- Purpose: Return validation
- Load at: Subagent execution only
Note: This skill is a thin wrapper. Context is loaded by the delegated agent, not this skill.
## Trigger Conditions
This skill activates when:
### Direct Invocation
- `/implement` command on a task with `language: founder` and `task_type: deck`
- Extension routing lookup finds `routing.implement["founder:deck"]`
### Language-Based Routing
- Task language is "founder" AND task_type is "deck"
- `/implement {N}` where task {N} has language="founder", task_type="deck"
### When NOT to trigger
Do not invoke for:
- Tasks with other task_types (market, analyze, strategy, legal, project, sheet, finance)
- Tasks with other language types (general, meta, neovim, etc.)
- Quick mode operations (`--quick` flag)
- Tasks in [NOT STARTED] status (need plan first)
- Tasks already [COMPLETED]
---
## Execution
### 1. Input Validation
Validate inputs from delegation context:
- `task_number` - Required, integer
- `plan_path` - Required, path to implementation plan
- `resume_phase` - Optional, phase number to resume from
- `session_id` - Required, string
```bash
# Validate task_number is present
if [ -z "$task_number" ]; then
return error "task_number is required"
fi
# Validate session_id is present
if [ -z "$session_id" ]; then
return error "session_id is required"
fi
# Validate plan_path exists
if [ -z "$plan_path" ] || [ ! -f "$plan_path" ]; then
return error "plan_path is required and must exist. Run /plan first."
fi
```
### 2. Preflight Status Update
Update task status to "implementing" in state.json:
```bash
jq --argjson num "$task_number" \
--arg ts "$(date -u +%Y-%m-%dT%H:%M:%SZ)" \
'(.active_projects[] | select(.project_number == $num)) += {
status: "implementing",
last_updated: $ts
}' specs/state.json > specs/tmp/state.json && mv specs/tmp/state.json specs/state.json
```
Update TODO.md status marker to [IMPLEMENTING].
### 3. Create Postflight Marker
Create marker file to signal postflight operations needed:
```bash
padded_num=$(printf "%03d" "$task_number")
project_name=$(jq -r --argjson num "$task_number" \
'.active_projects[] | select(.project_number == $num) | .project_name' \
specs/state.json)
task_dir="specs/${padded_num}_${project_name}"
mkdir -p "$task_dir"
cat > "$task_dir/.postflight-pending" << EOF
{
"session_id": "${session_id}",
"skill": "skill-deck-implement",
"task_number": ${task_number},
"operation": "implement",
"reason": "Postflight pending: status update, artifact linking, git commit",
"created": "$(date -u +%Y-%m-%dT%H:%M:%SZ)"
}
EOF
```
### 4. Context Preparation
Extract template palette from the plan file:
```bash
# Extract template palette from plan (look for "palette:" or "template:" in plan metadata)
template_palette=$(grep -oP '(?:palette|template):\s*\K[\w-]+' "$plan_path" | head -1)
template_palette="${template_palette:-dark-blue}"
# Extract forcing_data from state.json if available
forcing_data=$(jq -r --argjson num "$task_number" \
'.active_projects[] | select(.project_number == $num) | .forcing_data // null' \
specs/state.json)
```
Prepare delegation context for agent:
```json
{
"task_context": {
"task_number": 234,
"project_name": "seed_round_pitch_deck",
"description": "Seed round pitch deck",
"language": "founder",
"task_type": "deck"
},
"plan_path": "specs/234_seed_round_pitch_deck/plans/01_deck-plan.md",
"resume_phase": 1,
"output_dir": "strategy/",
"template_palette": "dark-blue",
"forcing_data": {
"purpose": "INVESTOR",
"source_materials": ["task:233"]
},
"metadata_file_path": "specs/234_seed_round_pitch_deck/.return-meta.json",
"metadata": {
"session_id": "sess_{timestamp}_{random}",
"delegation_depth": 2,
"delegation_path": ["orchestrator", "implement", "skill-deck-implement"]
}
}
```
### 5. Invoke Agent
**CRITICAL**: You MUST use the **Task** tool to spawn the agent.
**Required Tool Invocation**:
```
Tool: Task (NOT Skill)
Parameters:
- subagent_type: "deck-builder-agent"
- prompt: [Include task_context, plan_path, resume_phase, output_dir, template_palette, forcing_data, metadata]
- description: "Generate Slidev pitch deck from plan and research"
```
The agent will:
- Load plan and research report
- Load theme config from `.context/deck/themes/`
- Assemble `slides.md` from library content with slot filling
- Compose CSS styles and copy Vue components
- Attempt non-blocking `slidev export` for PDF
- Write-back new content to library
- Create summary in task directory
- Write metadata file for postflight consumption
- Return brief text summary
**Note**: Slidev export (PDF generation) is optional. Task completes successfully
even if slidev is not installed or PDF generation fails. The `slides.md` source is preserved.
### 6. Read Metadata File
After agent returns, read the metadata file:
```bash
metadata_file="specs/${padded_num}_${project_name}/.return-meta.json"
metadata=$(cat "$metadata_file")
status=$(echo "$metadata" | jq -r '.status')
```
### 7. Postflight Status Update
If agent succeeded (status == "implemented"):
```bash
# Update state.json to completed
jq --argjson num "$task_number" \
--arg ts "$(date -u +%Y-%m-%dT%H:%M:%SZ)" \
'(.active_projects[] | select(.project_number == $num)) += {
status: "completed",
last_updated: $ts
}' specs/state.json > specs/tmp/state.json && mv specs/tmp/state.json specs/state.json
# Link artifacts in state.json (deck files and summary)
artifacts=$(echo "$metadata" | jq '.artifacts')
for i in $(seq 0 $(($(echo "$artifacts" | jq 'length') - 1))); do
artifact_type=$(echo "$artifacts" | jq -r ".[$i].type")
artifact_path=$(echo "$artifacts" | jq -r ".[$i].path")
artifact_summary=$(echo "$artifacts" | jq -r ".[$i].summary")
jq --argjson num "$task_number" \
--arg type "$artifact_type" \
--arg path "$artifact_path" \
--arg summary "$artifact_summary" \
'(.active_projects[] | select(.project_number == $num)).artifacts += [{
type: $type,
path: $path,
summary: $summary
}]' specs/state.json > specs/tmp/state.json && mv specs/tmp/state.json specs/state.json
done
```
Update TODO.md status marker to [COMPLETED], add Completed date and Summary link.
If partial (status == "partial"):
- Keep status as "implementing"
- Note resume point in metadata
### 8. Git Commit
```bash
git add -A
git commit -m "$(cat <<'EOF'
task {N}: complete implementation
Session: {session_id}
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
EOF
)"
```
### 9. Cleanup and Return
Remove postflight markers and metadata:
```bash
rm -f "$task_dir/.postflight-pending"
rm -f "$task_dir/.postflight-loop-guard"
rm -f "$task_dir/.return-meta.json"
```
Return brief text summary to caller.
---
## Return Format
Brief text summary (NOT JSON).
Expected successful return (with PDF):
```
Deck implementation completed for task {N}:
- Theme: {theme_name}, Pattern: {pattern_name}
- Slides populated: {M}/{total} from research
- Slidev source: strategy/{slug}-deck/slides.md
- PDF: strategy/{slug}-deck/{slug}-deck.pdf
- Summary: specs/{NNN}_{SLUG}/summaries/01_{short-slug}-summary.md
- Status updated to [COMPLETED]
- Changes committed with session {session_id}
- Next: Review deck and fill remaining [TODO:] markers
```
Expected successful return (without PDF):
```
Deck implementation completed for task {N}:
- Theme: {theme_name}, Pattern: {pattern_name}
- Slides populated: {M}/{total} from research
- Slidev source: strategy/{slug}-deck/slides.md
- PDF: skipped (slidev not installed)
- Summary: specs/{NNN}_{SLUG}/summaries/01_{short-slug}-summary.md
- Status updated to [COMPLETED]
- Changes committed with session {session_id}
- Next: Install slidev for PDF export, or review slides.md source
```
Expected partial return:
```
Deck implementation partially completed for task {N}:
- Template selected but content generation incomplete
- Resume phase: {resume_phase}
- Status remains [IMPLEMENTING]
- Next: Run /implement {N} to resume
```
---
## Error Handling
### Session ID Missing
Return immediately with failed status.
### Plan Not Found
Return error with guidance to run /plan first.
### Task Not Found
Return error with guidance to check task number.
### Agent Errors
Pass through the agent's error return verbatim.
### Slidev/PDF Errors
PDF export failures do NOT block task completion:
- **Slidev not installed**: Task completes with `slides.md` source only
- **Export error**: Keep `slides.md` for debugging, task completes
- **PDF empty**: Keep `slides.md`, task completes
Postflight should check `metadata.pdf_generated` to determine what artifacts to report.Related Skills
skill-deck
Generate YC-style investor pitch decks in Typst
skill-team-implement
Orchestrate multi-agent implementation with parallel phase execution. Spawns teammates for independent phases and coordinates dependent phases. Includes debugger teammate for error recovery.
skill-implementer
Execute general implementation tasks following a plan. Invoke for general implementation work.
skill-z3-implementation
Implement Z3 constraints. Invoke for Z3-language implementation tasks.
skill-web-implementation
Implement web (Astro/Tailwind/TypeScript) changes following a plan. Invoke for web-language implementation tasks.
skill-typst-implementation
Implement Typst documents. Invoke for Typst-language implementation tasks.
skill-python-implementation
Implement Python code. Invoke for Python-language implementation tasks.
skill-neovim-implementation
Implement Neovim configuration changes from plans. Invoke for neovim implementation tasks.
skill-nix-implementation
Implement Nix configuration changes from plans. Invoke for nix implementation tasks.
skill-lean-implementation
Implement Lean 4 proofs and definitions using lean-lsp tools. Invoke for Lean-language implementation tasks.
skill-latex-implementation
Implement LaTeX documents. Invoke for LaTeX-language implementation tasks.
skill-founder-implement
Execute founder plans and generate strategy reports