software-toolkit

Plugin software-toolkit from marketplace jumptothecloud-code-marketplace in JumpToTheCloud/claude-code. Commands read from the repo's manifest — 12 days ago.

Skills (13)

• analyze

  Run a consistency analysis across a spec (GitHub issue written by /prd) and its technical plan (posted by /plan as a comment on the same issue). Detects duplication, ambiguity, underspecification, constitution violations, coverage gaps, and inconsistencies — then posts the findings back as a comment

• complete-feature

  Move a GitHub Feature (or Bug) to Status Done once its PR (feature/<n>-* or bugfix/<n>-*, opened by /execute-feature) has been merged into the base branch (next) — resolves the Feature from the PR or the PR from the Feature, gates on Issue Type, Phase Execution and Status In review (the only Status

• conventional-commits

  Guide for preparing atomic commits using Conventional Commits, with scopes discovered automatically from the repo structure.

• execute-feature

  Execute a whole GitHub Feature (or Bug) that /iteration-plan already broke down (Status Ready + Phase Execution) — checks the Feature's own blockers, builds the dependency tree of its native sub-issues, implements every reachable AFK sub-task (in parallel where independent, each in its own git workt

• grill-me

  Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".

• init-repo

  Initialize this repo's AGENTS.md/CLAUDE.md with its GitHub Component self-declaration and (optionally) its GitHub Project, so prd-to-issues can discover this repo. Use whenever the user wants to set up a repo for the prd/plan/analyze/prd-to-issues workflow, declare which Component this repo is, link

• iteration-plan

  Break a refined GitHub Feature or Bug (Status Ready + Phase Discovery, already processed by /refine-story) into technical sub-tasks — codebase analysis, TDD/branching decisions, native sub-issue hierarchy (addSubIssue) and dependencies (addBlockedBy), category and afk/hitl labels — then moves the Fe

• plan

  Turn a spec (GitHub issue written by /prd) into a structured technical plan with architecture decisions, affected modules, interface contracts, and phased implementation — then post it back as a comment on the same issue. Trigger this skill when the user says "/plan", "plan issue #N", "plan this PRD

• prd-to-issues

  Break a PRD (a GitHub issue written by /prd) into independently-grabbable issues using tracer-bullet vertical slices, created with the native "Feature" Issue Type, an afk/hitl label, a per-PRD Milestone, and native GitHub issue dependencies, in the repo its Component maps to, added to the team's sha

• prd

  Convert a feature idea or description into a Product Requirements Document (PRD) and publish it as a GitHub issue with the native "PRD" Issue Type, added to the team's shared GitHub Project with its Component, Phase, and Status fields set. Use whenever the user wants to write a PRD, spec, or specifi

• refine-story

  Refine a GitHub Feature issue (created by /prd-to-issues) or Bug issue (created by /report-bug) into something ready to implement — full FR/NFR extraction, enriched Acceptance Criteria, Size/Estimate/Priority fields set, named assumptions instead of open questions. Moves Status from Backlog through

• report-bug

  File a bug found during review, while executing a Feature, or in a release candidate as a GitHub issue with the native "Bug" Issue Type — reproduction steps, expected vs actual behavior, affected files, Given/When/Then acceptance criteria including a regression test, an afk/hitl label, added to the

• tdd

  Test-driven development with red-green-refactor loop. Use when the user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development. Also use whenever you are implementing a GitHub issue (a Feature from /refine-story or a

Subagents (7)

• analyze

  Use this agent to cross-check a GitHub issue's spec and its technical plan comment for quality issues (duplication, ambiguity, gaps, constitution violations) before running /prd-to-issues. Delegate to it whenever the user wants to analyze a PRD issue, validate a spec against its plan, or check if a

• conventional-commits

  Use this agent to prepare and execute git commits following the Conventional Commits format. Delegate to it whenever the user wants to commit changes, split staged/unstaged work into atomic commits, review a commit strategy, or plan commit scopes before pushing. It analyzes the diff, groups changes

• init-repo

  Use this agent to declare a repo's GitHub Component (and optionally its GitHub Project) in AGENTS.md/CLAUDE.md. Delegate to it whenever the user wants to set up a repo for the prd/plan/analyze/prd-to-issues workflow or register which Component a repo is.

• iteration-plan

  Use this agent to break a refined GitHub Feature or Bug (Status Ready + Phase Discovery) into technical sub-tasks — codebase analysis, native sub-issue hierarchy (addSubIssue) and dependencies (addBlockedBy), category and afk/hitl labels — then move the Feature itself to Status Ready + Phase Executi

• prd-to-issues

  Use this agent to break a GitHub PRD issue into vertical-slice implementation issues (native "Feature" Issue Type, an afk/hitl label, a per-PRD Milestone, and native GitHub issue dependencies) in the repo its Component maps to, added to the shared GitHub Project. Delegate to it whenever the user wan

• refine-story

  Use this agent to refine a GitHub Feature or Bug issue into something ready to implement — full FR/NFR extraction, enriched Acceptance Criteria, Size/Estimate/Priority set, Status moved from Backlog through Refining to Ready. Given an issue number, refines that one Feature; given none, refines every

• task-executor

  Use this agent to implement exactly one GitHub sub-task inside a git worktree that /execute-feature already prepared — test-first with the tdd skill when the sub-task carries the tdd label, otherwise implementation, integration tests or docs per its category — committing with Conventional Commits an

Hooks (1)

• PreToolUse

  ${CLAUDE_PLUGIN_ROOT}/hooks/approve-own-skills.sh

Similar plugins