ank

ANK Skills

These are the skills I've formalised to make my own agentic workflow smoother and more efficient. Small, focused, composable — meant to slot into whatever I'm building rather than own the process. If any of them are useful to you too, take them, fork them, change them.

Quickstart

Pick one of the two install paths:

Claude Code plugin (native):

# In Claude Code:
/plugin marketplace add ananthanandanan/skills
/plugin install ank@ank-skills

Skills then appear namespaced as /ank:<skill> (e.g. /ank:review-board, /ank:handoff).

npx skills installer:

npx skills@latest add ananthanandanan/skills

Then pick the skills you want from the interactive list.

Skills

Engineering

• /review-board — generates a single-file HTML "story-paced walkthrough" of a finished feature for human code review. Sidebar nav, Why/Tradeoff/Deferred callouts, status pills, reviewer's checklist. Use it after finishing a feature or merging a PR, when a teammate needs to understand the why and the shape of the change, not just the diff.
• /handoff — drops a Markdown handoff doc at docs/<slug>-handoff.md distilling the current conversation (agenda, files touched, bugs, fixes, decisions, current state, next steps) so another agent — Claude, Codex, opencode, pi, ampcode, Cursor, or a fresh session — can resume without re-deriving context. Invoke when your context window is nearly full.
• /third-degree — interviews you one question at a time, walking the decision tree until the spec is sharp. Each question comes with structured options and a recommended pick; anything the codebase already answers is inferred rather than asked. Front of the pipeline — invoke when the idea is fuzzy, before /spec or /visualise-plan.
• /spec — turns a rough product idea (or a /third-degree summary) into a single opinionated SPEC.md at repo root (or docs/spec/<slug>.md for feature scope). One required-section list covers both library/SDK shapes and SaaS/app shapes; conditional sections (data model, API endpoints, frontend, pricing, success metrics) kick in based on what the product actually needs. Hard-stops until you reply "approved" — then /tasks picks up.
• /tasks — turns an approved SPEC.md into TASKS.md (phases, parallel tracks, sized tasks, dependency map), then creates matching GitHub issues, a Project board, and empty-directory scaffolding from the spec's package layout. Confirms before any gh side-effect; degrades gracefully when gh is missing — it writes TASKS.md and asks you to gh auth login then re-run.
• /visualise-plan — produces a single-file HTML implementation plan at docs/plan/<slug>.html (Botanical Almanac styling: milestones, data-flow SVG, mockups, files-touched list, key code). Use for feature-level planning when you want a visual artifact to review before writing code. Hard-stops until you reply "approved".

Authoring a new skill

Add a directory under skills/<category>/<name>/ with a SKILL.md (YAML frontmatter must include name and description — CI enforces this), then append the path to the skills array in .claude-plugin/plugin.json. The review-board skill is the reference layout.