Explore skills

Translate between Cantonese and other languages (Mandarin, English, etc.). Use when user explicitly requests translation or when translation is needed for communication.

Turn the current conversation context into a GSD-compatible PRD with WHAT/HOW constraints, optionally writing to .harness/phases/01-discuss/CONTEXT.md. Use when user wants to create a PRD from the current context.

Rewrite docstrings and comments by reading the actual implementation, call sites, and tests — produce grounded, factual prose instead of deleting slop. Sibling of /techne:deslop. Use when the user wants to replace overhyped or hallucinated documentation with accurate one- or two-line descriptions derived from what the code actually does.

Check a documentation file for drift against the actual codebase — CLI commands, file paths, config keys, function signatures, version numbers, environment variables — and propose corrections. Use when the user wants to audit README.md, docs/*.md, or similar for claims that no longer match reality. Drift usually comes from refactors that forgot to update the docs.

Maintain the Zensical-powered documentation site — nav ordering in zensical.toml, the docs GitHub Pages workflow, CSS and JS assets, and link/anchor integrity across docs/**/*.md. Sibling of /techne:docsync (which only verifies prose claims against code). Use when the user wants the site itself audited — config, deploy pipeline, theming, assets, cross-page links — rather than content accuracy.

Define the reader/customer avatar, painful current state, desired outcome, transformation bridge, objections, and proof needed before writing profile copy, posts, articles, landing pages, or visual concepts.

Amazon''s Working Backwards product development method based on Colin Bryar and Bill Carr''s "Working Backwards". Use this skill whenever the user is discussing a new product, feature, pitch, or launch narrative — even if they do not explicitly say "PR/FAQ," "press release," or "working backwards." Triggers include: (1) writing or reviewing a PR/FAQ for a new product or feature, (2) drafting the l