skills

vpaivag/skills

Personal collection of agent skills covering planning, repo setup, and onboarding workflows.

Each skill is a self-contained SKILL.md under skills/<name>/ that loads on demand when its trigger fires. The planning skills compose into one loop:

flowchart TD
    intake[/intake/]
    simple[/simple-plan/]
    deep[/deep-plan/]
    execute[/execute-plan/]
    review[/review-plan/]
    tracker(plan-tracker)

    intake -->|straightforward| simple
    intake -->|ADR-gate fires| deep
    deep --> execute
    execute --> review

    deep -.reads-output.-> tracker
    tracker -.tracks-changes.-> execute

    classDef helper fill:#f5f5f5,stroke:#999,stroke-dasharray:4 3,color:#555
    class tracker helper

Diagram shows the planning loop; see the clusters below for setup and onboarding skills.

/intake is the recommended front door — it gathers context and points you at the right planner. You can still invoke /deep-plan or /simple-plan directly if you already know which one fits.

Contents

• Install
  • Via the skills CLI
  • As a Claude Code plugin
• Skills
  • Planning
    • intake
    • simple-plan
    • deep-plan
    • execute-plan
    • plan-tracker
    • review-plan
  • Repo setup
    • setup
    • claude-md-refactor
  • Onboarding
    • onboarding
  • Standalone
    • pr-reviewer
• Layout
• Contributing

Install

Pick the path that matches your setup:

Via the skills CLI

Manually add the skills to any agent using the skills CLI.

Install all skills:

npx skills@latest add vpaivag/skills

Install a specific skill:

npx skills@latest add vpaivag/skills --skill deep-plan

Target a specific agent (e.g. Claude Code):

npx skills@latest add vpaivag/skills -a claude-code

As a Claude Code plugin

This repo is a Claude Code plugin marketplace. Run each command on its own line at the Claude Code prompt:

/plugin marketplace add vpaivag/skills

/plugin install skills@vpaivag

/reload-plugins

The first command registers the marketplace (named vpaivag) by fetching .claude-plugin/marketplace.json from this repo. The second installs the skills plugin from it. The third activates the plugin in your current session — without a restart.

Verify it's registered:

/plugin marketplace list

If /plugin install skills@vpaivag returns Marketplace "vpaivag" not found, the marketplace add step didn't complete — re-run it and check the output.

Update later:

/plugin marketplace update vpaivag

Or use a local clone instead of GitHub:

/plugin marketplace add /absolute/path/to/skills

Skills

Planning

intake

Trigger: /intake or asking to "start a new task", "scope this out", or wanting help deciding whether a task needs a deep plan.

Short, focused Q&A front door for any new task. Asks up to a handful of clarifying questions, writes a context.md capturing the task and the resolved assumptions, then recommends either /simple-plan or /deep-plan based on an ADR-gate (hard-to-reverse, surprising-without-context, real-tradeoff, or cross-concern — task spans multiple distinct kinds of change). File count is deliberately not a criterion: a 30-file uniform rename stays in /simple-plan. The downstream planner adopts the same suite directory, so no context is lost between intake and planning.

Highlights:

• Capped questions. Won't grill you — gathers just enough to disambiguate.
• Picks the right planner. ADR-gate rules pick /deep-plan only when it's actually warranted, otherwise routes to /simple-plan.
• Hands off cleanly. Writes context.md into a suite dir the planner picks up automatically.

→ skills/intake

simple-plan

Trigger: /simple-plan or asking for a lightweight plan for a straightforward task.

Lightweight planner for mechanical or bounded tasks where /deep-plan's full Restate → Explore → Design → Specify → Risk → Verify treatment is overkill. Produces a single simple-plan.md in a suite directory and, if you approve, implements it in the same session — no /execute-plan handoff, no chunk decomposition, no index.md (so /plan-tracker and /execute-plan ignore it by design).

Use this when the work is mechanical (rename a field across a codebase), a small bug fix, a one-file addition, or otherwise lacks real design choices. If a task turns out to be deeper than expected, switch to /deep-plan.

→ skills/simple-plan

deep-plan