MeatySkills

Token-efficient tracking for AI orchestration. CLI-first for status updates (~50 tokens), agent fallback for complex ops (~1KB). Use when: updating task status, querying blockers, creating progress files, validating phases.

Unified execution engine for all development workflows. Progressive disclosure for phase execution, quick features, story completion, and scaffolding. Integrates with artifact-tracking and meatycapture-capture. Use when running /dev:execute-phase, /dev:quick-feature, /dev:implement-story, /dev:complete-user-story, or /dev:create-feature commands.

Generate and optimize PRDs, Implementation Plans, and Progress Tracking documents optimized as AI artifacts for development agents. Use when creating new feature plans, breaking down long planning docs (>800 lines), or setting up progress tracking. Supports: 1) Create PRD from feature request, 2) Create Implementation Plan from PRD with phase breakdown and subagent assignments, 3) Optimize existing plans by breaking into phase-specific files, 4) Create progress tracking with task assignments. Example: "Create a PRD for user authentication feature" or "Break down the sidebar-polish implementation plan into phase files" or "Create progress tracking for data-layer-fixes PRD".

Use this skill when authoring, modifying, or validating SkillMeat Dynamic Workflow scripts (.claude/workflows/*.js). Covers the full governed procedure: loading the master contract and per-workflow spec, choosing patterns from the pattern library, generating scripts against ExecutionGraph/ExecutionReport schemas, validating against the four-constraints checklist (no FS/shell in script, Mode D as boundary, edit-less reviewers, no Date.now/Math.random), syntax-check recipe (async-IIFE wrap for node --check), dry-run guidance, saving to .claude/workflows/, and registering in workflow-registry.md. Use whenever creating a new workflow, extending an existing one, or reviewing a workflow script for compliance.

Delegate bounded subtasks to IBM Bob Shell CLI. Use when the user wants to use Bob, delegate to Bob, run Bob for drafting/scaffolding/exploration, or compare Claude Code work with Bob output. Do NOT use for architecture-heavy integration work or cross-layer backend changes.

Answer CCDash project-intelligence questions using the shipped MCP tools when available and the in-repo `ccdash` CLI otherwise. Use when the operator or another agent asks about project status, feature forensics, workflow failure patterns, after-action reports, artifact intelligence, live agent counts, system metrics, runtime validation posture, CLI timeout or caching behavior, project registration, or how to troubleshoot the shipped CCDash API/worker/MCP surfaces. Keep routing aligned with the current shipped runtime contract and repo docs.

Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.

Audits CHANGELOG coverage for a git commit range; read-only — surfaces gaps for human remediation. Use this skill before a version bump, in CI, or ad-hoc to verify that all non-trivial commits are reflected in the changelog. Co-loaded with the release skill on every /release:bump invocation. Does not write or modify any files; outputs structured gap reports and exit codes only.

Integrate Claude Agent SDK into Python apps with subscription OAuth, structured output, MCP tools, and provider abstraction. Captures production-validated patterns and bug workarounds. Use when adding Claude Agent SDK to a Python application, enabling Claude subscription auth (OAuth) alongside API key auth, building multi-turn agent workflows with tool use, integrating MCP tools, or setting up provider abstraction.

Expert reference for Claude Code itself — features, setup, troubleshooting, and enterprise use. Use this skill when answering questions about Claude Code installation, authentication, slash commands, agent skills, MCP server configuration, hooks, plugins, IDE integration (VS Code, JetBrains), CI/CD integration, enterprise deployment (SSO, sandboxing, monitoring), extended thinking, caching, checkpointing, cost tracking, or debugging Claude Code behaviour. Distinct from the user-level Extensibility skill: this skill is about operating and understanding Claude Code, not about authoring new extensions.

Debug and remediate bugs with severity-gated workflows. Progressive disclosure from quick triage through comprehensive remediation planning. Integrates with planning skill for complex fixes and artifact-tracking for progress. Use when running /fix:debug or /fix:bugfix-commit commands.

Create, maintain, and review software application demos as versioned, executable product artifacts. Generates repeatable screenshots, browser walkthrough videos, animations, voiceover scripts, captions, thumbnails, talking points, and review reports from scenario manifests using Playwright + Remotion + FFmpeg pipelines. Use when the user asks to build/refresh/review a demo, capture screenshots or a walkthrough video, scaffold demo infrastructure, or wire demo workflows into CI. Dry-run first; only writes files on explicit apply/setup/initialize requests.

Use this skill to generate well-branded interfaces and assets for IBM Consulting, either for production or throwaway prototypes/mocks/etc. Contains essential design guidelines, colors, type, fonts, assets, and UI kit components for prototyping. Rooted in IBM's open Carbon Design System and the IBM Plex type family.

Create, rebuild, or maintain a project README using a modular Handlebars build system. Covers bootstrapping the .github/readme/ scaffold for any project, planning screenshot and GIF visual assets, crafting content strategy (audience analysis, section structure, success metrics), assembling or rebuilding README.md from partials and data files, validating links and screenshots, and wiring CI workflows or pre-commit hooks for README freshness. Also use when a version bump, feature addition, or screenshot update requires regenerating README content. Supports CLI tools, web apps, libraries, and SaaS products.

Capture bugs/enhancements/ideas to request-logs. For quick operations use /mc command instead.

Drive the MeatyWiki CLI end-to-end — knowledge-compilation loop (ingest → classify → extract → compile → file-back → lint) over a file-first Obsidian-compatible markdown vault. Use when running any MeatyWiki CLI task, compiling inbox sources, querying/searching the wiki, or orchestrating the compile loop. Triggers: "meatywiki", "compile loop", "ingest into wiki", "vault", "knowledge compilation". Do NOT use for: non-MeatyWiki knowledge systems, Portal UI, SAM/CCDash (those are separate skills/projects).

Full-lifecycle MeatyWiki usage — compilation engine CLI, Portal REST API, and MCP server. Use when: running any MeatyWiki CLI command, calling Portal API endpoints, performing vault CRUD, ingesting content, compiling artifacts, querying knowledge, managing workflows, or deploying MeatyWiki for agentic use.

Deploy and manage NotebookLM documentation sync for any Claude Code project. Installs Python scripts + Claude Code hook that automatically syncs markdown files to a Google NotebookLM notebook on every Write/Edit. Supports install, status, resync, batch sync, cleanup, and uninstall workflows. Use when setting up NotebookLM sync in a new project, checking sync health, or managing notebook sources.

Post-implementation retrospective on a completed implementation plan. Compares estimated story points against measured complexity (git stats, file counts, CCDash AAR), identifies which estimation heuristics failed, and emits actionable tuning suggestions for the planning skill. Use when a feature is done or near-done and the user asks for a retrospective ("why did X take so long", "review the plan for X", "AAR on X", "what did we miss in the estimate"), or proactively after any plan ≥5 pts completes. Complements CCDash's `feature-retrospective` recipe by adding heuristic-tuning analysis specific to SkillMeat's planning skill.

Cross-feature visibility layer for implementation plans, PRDs, and progress files. Use when: checking what's in progress, auditing stale plan statuses, remediating mismatches between frontmatter and task reality, summarizing active work, investigating orphaned/superseded PRDs. Complements artifact-tracking (which handles per-phase task updates). Routes intent to scripts/plan-status-report.py and artifact-tracking scripts.

Use this skill to distill a software project (codebase plus optional supplemental docs, ADRs, PRDs, NotebookLM exports, design/business notes) into high-signal, research-ready context artifacts. Produces four synthesized markdown documents — feature catalog, design fundamentals, research context pack, and opportunity map — grounded in repo evidence with explicit confidence levels, intended for downstream AI agents reasoning about expansion, novel ideas, or architectural evolution. Trigger when the user asks to "distill project context", "generate project understanding artifacts", "externalize project context for future agents", "build a research context pack", or points the skill at a repo with supplemental materials.

Recover from crashed, failed, or interrupted Claude Code sessions. Use this skill when: session crashed during multi-agent parallel execution, need to determine what work was completed vs incomplete, want to generate resumption commands for interrupted tasks, recovering from context window exhaustion, or handling session handoffs. Analyzes agent logs, verifies on-disk state, and creates resumption plans with ready-to-execute Task() commands.

End-to-end release orchestration for SkillMeat. Routes five intents (version bump, regen openapi, regen SDK, audit coverage, rollover changelog) to the single linear release-orchestration workflow. Use when running /release:bump or coordinating a tagged release.

Manage SkillMeat and Claude Code environments through natural language. Use this skill for artifact discovery, deployment, management, bundle/scaffold operations, memory and context workflows, supply-chain security, versioning, authentication, attestation, and enterprise migration. Progressive disclosure: load only the workflow doc needed for the current intent.

Use this skill when scaffolding a new project or feature from context (PRD, implementation plan, project directory, or free-text description). Transforms context into a deployed Bundle of artifacts via structured Intent extraction and ranked artifact search. Invoked by /scaffold:project and /scaffold:feature commands. Trigger phrases: 'scaffold my project', 'set up my Claude environment', 'create a starter bundle', 'scaffold from my PRD', 'build my artifact bundle', 'feature scaffold', 'scaffold feature'. Requires a seeded local collection (≥20 artifacts) and a running SkillMeat API.