signal_to_system

Use this skill when creating, updating, or querying AI-optimized tracking artifacts. Invoke for: creating phase progress tracking, updating task status, querying pending/blocked tasks, generating session handoffs, validating artifacts, or understanding how to use progress files for orchestration. Provides YAML+Markdown hybrid format with 95% token reduction. Core functions: CREATE, UPDATE, QUERY, VALIDATE, ORCHESTRATE.

Orchestrate the full blog workflow for Signal to System: from post conception through design, drafting, editorial review/revision, and publication prep. Use when starting a new post from a topic, continuing from a spec, reviewing/revising an existing draft, or preparing content for publication. Coordinates drafting, voice calibration, review feedback, series continuity, and publication preparation. Handles all content phases (design → draft → review → publish) and editorial modes (review, revise, story-craft).

Drive the standalone CCDash CLI from natural language to answer questions about project status, feature forensics, agent sessions, workflow failures, and after-action reports. Use when the operator or another agent asks about CCDash project health, agent-session analytics ("why did FEAT-X take so long", "what sessions ran for this feature", "which workflows are failing"), wants an AAR / narrative feature report, or needs help installing / authenticating the `ccdash` CLI against a target server. Routes intent to `ccdash` subcommands with the right `--output` mode, echoes provenance IDs for chaining, and degrades gracefully through `ccdash doctor` on transport/auth failures. Do not use for unrelated coding tasks, writing UI components, or anything outside CCDash project/session intelligence.

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.

Apply a naturalness and humanization pass to blog drafts to reduce AI-detectable patterns. Use after /voice-writer has produced a draft, or on any content that reads too much like polished AI output. Preserves Nick Miethe's voice characteristics while adding sentence variation, unexpected word choices, natural imperfections, and conversational flow. Works best when applied to drafts that are already technically sound and voice-calibrated.

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 (including semantic/vector search), checking lens scores, managing workflow runs, or evaluating decisions. Triggers: "meatywiki", "compile loop", "ingest into wiki", "vault", "knowledge compilation", "semantic search", "lens score", "fidelity", "freshness", "workflow run", "decision table". Do NOT use for: non-MeatyWiki knowledge systems, Portal UI, SAM/CCDash (those are separate skills/projects).

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 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 Codex 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.

Use this skill when creating new Codex skills from scratch, editing existing skills to improve their descriptions or structure, or converting Codex sub-agents to skills. This includes designing skill workflows, writing SKILL.md files, organizing supporting files with intention-revealing names, and leveraging CLI tools and Node.js scripting.

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Codex's capabilities with specialized knowledge, workflows, or tool integrations.

Run all necessary artifact updates after code changes following MP patterns

Writes or edits blog content in Nick Miethe's authentic voice for the Signal to System publication. This skill should be used when drafting new posts, editing existing drafts to better match Nick's voice, or reviewing content for voice consistency. Triggers on requests like "write a post about X", "draft this in my voice", "edit this to sound more like me", "make this match my style", or any content authoring task for Signal to System. Reads the voice specification and published posts before writing to ensure output is calibrated to Nick's actual patterns, not a generic approximation of them.

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".

Orchestrate the full blog workflow for Signal to System: from post conception through design, drafting, editorial review/revision, and publication prep. Use when starting a new post from a topic, continuing from a spec, reviewing/revising an existing draft, or preparing content for publication. Coordinates drafting, voice calibration, review feedback, series continuity, and publication preparation. Handles all content phases (design → draft → review → publish) and editorial modes (review, revise, story-craft).

Use this skill when creating, updating, or querying AI-optimized tracking artifacts. Invoke for: creating phase progress tracking, updating task status, querying pending/blocked tasks, generating session handoffs, validating artifacts, or understanding how to use progress files for orchestration. Provides YAML+Markdown hybrid format with 95% token reduction. Core functions: CREATE, UPDATE, QUERY, VALIDATE, ORCHESTRATE.

Use this skill when creating new Claude Code skills from scratch, editing existing skills to improve their descriptions or structure, or converting Claude Code sub-agents to skills. This includes designing skill workflows, writing SKILL.md files, organizing supporting files with intention-revealing names, and leveraging CLI tools and Node.js scripting.