index.json

{
  "version": "0.16.0",
  "package": "@tdwhere/do-it",
  "repository": "https://github.com/tdwhere123/do-it",
  "domain": "agentic-workflow",
  "total_skills": 11,
  "total_capabilities": 11,
  "total_discovery_entries": 1,
  "total_agents": 10,
  "coverage": {
    "skill_groups": {
      "index": 1,
      "mainline": 7,
      "maintenance": 3,
      "on-demand": 1
    },
    "optional_skills": []
  },
  "entries": [
    {
      "kind": "skill",
      "name": "do-it-skills-index",
      "description": "Generated compact index for lazy do-it skill discovery.",
      "origin": "do-it",
      "optional": false,
      "group": "index",
      "source": "dist/claude/skills/_index.md",
      "target": "skills/_index.md"
    },
    {
      "kind": "skill",
      "name": "do-it-router",
      "description": "Use when starting any non-trivial repo task: pick Light / Standard / Heavy tier, then self-select meaning skills — not a fixed pipeline.",
      "origin": "do-it",
      "optional": false,
      "group": "mainline",
      "source": "skills/do-it/do-it-router",
      "target": "skills/do-it-router"
    },
    {
      "kind": "skill",
      "name": "do-it-core",
      "description": "Use when starting non-trivial repo work or making a done/fixed/ready/merge claim: apply the universal evidence, scope, boundary, recovery, verification, and reporting rules.",
      "origin": "do-it",
      "optional": false,
      "group": "mainline",
      "source": "skills/do-it/do-it-core",
      "target": "skills/do-it-core"
    },
    {
      "kind": "skill",
      "name": "do-it-architecture",
      "description": "Use when work changes or evaluates load-bearing authority, ownership, public or persisted contracts, dependency boundaries, migration/cutover, recovery, guards, or structural deletion.",
      "origin": "do-it",
      "optional": false,
      "group": "mainline",
      "source": "skills/do-it/do-it-architecture",
      "target": "skills/do-it-architecture"
    },
    {
      "kind": "skill",
      "name": "do-it-code-quality",
      "description": "Use when writing or designing code: name premise and blast radius, deepen modules at seams, TDD at agreed seams, diagnose before patching, and keep producer→consumer contracts honest.",
      "origin": "do-it",
      "optional": false,
      "group": "mainline",
      "source": "skills/do-it/do-it-code-quality",
      "target": "skills/do-it-code-quality"
    },
    {
      "kind": "skill",
      "name": "do-it-review",
      "description": "Use when a diff needs PR-style review, or findings need atomic repair and same-scope re-review — Standards axis and Spec axis, kept separate.",
      "origin": "do-it",
      "optional": false,
      "group": "mainline",
      "source": "skills/do-it/do-it-review",
      "target": "skills/do-it-review"
    },
    {
      "kind": "skill",
      "name": "do-it-decide",
      "description": "Use when premises or options must be pressure-tested, a short plan/handoff is needed, or a large plan must be sliced — grill facts locally, ask decisions one at a time.",
      "origin": "do-it",
      "optional": false,
      "group": "mainline",
      "source": "skills/do-it/do-it-decide",
      "target": "skills/do-it-decide"
    },
    {
      "kind": "skill",
      "name": "do-it-verify",
      "description": "Use before any done, fixed, passing, ready, install, or merge claim, and when closing a branch — fresh evidence on this worktree; hooks vary by host, this skill is the checklist.",
      "origin": "do-it",
      "optional": false,
      "group": "mainline",
      "source": "skills/do-it/do-it-verify",
      "target": "skills/do-it-verify"
    },
    {
      "kind": "skill",
      "name": "do-it-retrospective",
      "description": "Use only when the user explicitly asks to enable, disable, inspect, report, or persist opt-in local do-it behavioral feedback.",
      "origin": "do-it",
      "optional": false,
      "group": "on-demand",
      "source": "skills/do-it/do-it-retrospective",
      "target": "skills/do-it-retrospective"
    },
    {
      "kind": "skill",
      "name": "do-it-context",
      "description": "Use when repo terms or invariants are drifting, or when user/docs/code naming disagrees and a canonical glossary is needed — `.do-it/CONTEXT.md` is the downstream source of truth for names, relationships, and facts.",
      "origin": "do-it",
      "optional": false,
      "group": "maintenance",
      "source": "skills/do-it/do-it-context",
      "target": "skills/do-it-context"
    },
    {
      "kind": "skill",
      "name": "do-it-handbook",
      "description": "Use when a project needs a lean `.do-it/handbook/` for stable project truth plus `.do-it/worklog/` for daily or goal notes.",
      "origin": "do-it",
      "optional": false,
      "group": "maintenance",
      "source": "skills/do-it/do-it-handbook",
      "target": "skills/do-it-handbook"
    },
    {
      "kind": "skill",
      "name": "do-it-skill-authoring",
      "description": "Use when creating or updating do-it skills: write predictable model-invoked descriptions, progressive disclosure, leading words, and hook-aware escape behavior.",
      "origin": "do-it",
      "optional": false,
      "group": "maintenance",
      "source": "skills/do-it/do-it-skill-authoring",
      "target": "skills/do-it-skill-authoring"
    },
    {
      "kind": "agent",
      "name": "architecture-strategist",
      "description": "Use when an architectural choice or stage boundary needs a read-only view of invariants, ownership, extension seams, and proof.",
      "origin": "do-it",
      "optional": false,
      "source": "agents/architecture-strategist.toml",
      "target": "agents/architecture-strategist.toml"
    },
    {
      "kind": "agent",
      "name": "code-mapper",
      "description": "Use when quick reconnaissance is complete and an unfamiliar or risky bounded scope needs a read-only trace or thorough map of ownership, contracts, consumers, and unknowns.",
      "origin": "do-it",
      "optional": false,
      "source": "agents/code-mapper.toml",
      "target": "agents/code-mapper.toml"
    },
    {
      "kind": "agent",
      "name": "code-quality-cleaner",
      "description": "Use when a diff needs a read-only maintainability review for dead code, duplication, needless abstraction, reinvented primitives, and safe simplification.",
      "origin": "do-it",
      "optional": false,
      "source": "agents/code-quality-cleaner.toml",
      "target": "agents/code-quality-cleaner.toml"
    },
    {
      "kind": "agent",
      "name": "documentation-engineer",
      "description": "Use when documentation must be updated to accurately reflect verified repository behavior, tooling, installation, or operator workflows.",
      "origin": "do-it",
      "optional": false,
      "source": "agents/documentation-engineer.toml",
      "target": "agents/documentation-engineer.toml"
    },
    {
      "kind": "agent",
      "name": "plan-challenger",
      "description": "Use when a proposed plan needs a read-only challenge of outcome, scope, acceptance, risk, and cheaper credible alternatives.",
      "origin": "do-it",
      "optional": false,
      "source": "agents/plan-challenger.toml",
      "target": "agents/plan-challenger.toml"
    },
    {
      "kind": "agent",
      "name": "product-strategist",
      "description": "Use when a feature or decision needs a read-only product lens on user goal, boundary, viable options, and tradeoffs.",
      "origin": "do-it",
      "optional": false,
      "source": "agents/product-strategist.toml",
      "target": "agents/product-strategist.toml"
    },
    {
      "kind": "agent",
      "name": "red-team-reviewer",
      "description": "Use when a change or design needs a read-only adversarial review of trust boundaries, failures, state, persistence, concurrency, or replay.",
      "origin": "do-it",
      "optional": false,
      "source": "agents/red-team-reviewer.toml",
      "target": "agents/red-team-reviewer.toml"
    },
    {
      "kind": "agent",
      "name": "reviewer",
      "description": "Use when a diff or delivered behavior needs a read-only correctness review for reachability, contract regressions, errors, and missing proof.",
      "origin": "do-it",
      "optional": false,
      "source": "agents/reviewer.toml",
      "target": "agents/reviewer.toml"
    },
    {
      "kind": "agent",
      "name": "spec-compliance-reviewer",
      "description": "Use when a delivered change needs a read-only check against the written task, acceptance criteria, explicit deferrals, and ownership boundaries.",
      "origin": "do-it",
      "optional": false,
      "source": "agents/spec-compliance-reviewer.toml",
      "target": "agents/spec-compliance-reviewer.toml"
    },
    {
      "kind": "agent",
      "name": "tdd-red-writer",
      "description": "Use when a behavior change benefits from a narrow failing test before implementation and a test-only write scope is available.",
      "origin": "do-it",
      "optional": false,
      "source": "agents/tdd-red-writer.toml",
      "target": "agents/tdd-red-writer.toml"
    }
  ]
}