Drive a whole phase or feature-set to "merged + Done" — themed batching over /drive, front-loaded architectural questions, phase-gate ceremonies, and lossless resume. The long-horizon recipe ABOVE /drive; pair with native /goal " delivered" for hands-off, multi-turn completion.
Drive one tracker ticket end-to-end — claim, plan, implement, verify, cross-review, and ship — autonomously, pausing only for architectural decisions. The per-ticket recipe; pair with native /goal " is merged" for unattended multi-turn completion.
Draft an ephemeral ADR for an in-flight architectural decision (--draft), then propagate the accepted decision to SPEC + PRD + phases.yaml + tracker bodies atomically (--apply ) via the apply-decision verb's resumable journal.
A structured conversation and documentation tool for creating a software requirements specification, or SRS. An SRS records users, goals, scope, workflows, rules, permissions, exceptions, and acceptance needs before technical design or coding.
A planning guide for splitting a hardware or embedded-system project into separately deliverable OpenSpec changes, which are structured implementation proposals.
Read Google Docs, Sheets, and Slides via the gws CLI, and search for files across Google Drive (including Shared Drives). Converts content to clean markdown. Use this skill when the user asks to "read a Google Doc", "grab that spreadsheet", "find a file on Drive", "search Drive for...", or when any CKW command needs…
Upload files to Google Drive and create Google Docs from markdown via the gws CLI. Use this skill when the user asks to "upload to Drive", "push this to Drive", "share this on Drive", or when any CKW command needs to send files to Google Workspace (e.g., export-document --to-drive).
Publish markdown drafts to Proof (proofeditor.ai) for collaborative review with AI provenance tracking. Use this skill when the user asks to "publish to Proof", "share a draft for review", or when the /ckw:publish-proof command needs to create or update Proof documents.
The design-first development route — walk a pain point through brainstorm → design (parallel wireframes → pick → hi-fi mockup) → plan, so you see what the thing looks like before writing code, and hold the build to that design with screenshot comparison. Drives a local Open Design daemon to produce previewable HTML…
Open the current design artifact in the Open Design browser portal so a human can mark it up, comment on elements, or edit it directly — then pick the work back up in the terminal without losing what changed. Use when the user types "/ce-markup", or says "let me mark this up", "open it in the browser", "I want to…