jira

Plugin jira from marketplace claudefiles in koolamusic/claudefiles. Commands read from the repo's manifest — 29 days ago.

Slash commands (13)

• /jira:advisor

  Advisory gate for triage or plan decisions. Spawns a second-opinion agent that challenges assumptions, surfaces risks, and proposes alternatives before the decision commits. Based on Anthropic advisor tool pattern.

• /jira:comment

  Draft or post a GitHub issue/PR comment in stakeholder-readable voice, with proper GitHub autolinks and code permalinks. Default is draft-for-approval; posting is opt-in.

• /jira:execute

  Execute the active sprint wave-by-wave with parallel jira-executor instances per wave. Then jira-nyquist (test gates), then jira-verifier (goal-backward), then PR. Updates STATE.md throughout.

• /jira:flow

  Generate FLOW.md — human verification steps for the active sprint's acceptance predicates. Thinks like a tester; where to log in, what to click, which route to visit. Prioritizes predicates machines couldn't sense. Middleware between features/ and warden design.

• /jira:init

  Bootstrap .jira/ in the current repo. Idempotent. Creates .jira/{.gitignore, README.md, STATE.md, sprints/, CURRENT}.

• /jira:issue

  Draft a GitHub issue from the active sprint's research, plan, or wave — following the evidence-grounded conventions in templates/issue/GUIDE.md. Saves a draft; push is opt-in.

• /jira:paper

  Write an evidence-disciplined engineering paper (innovation/discovery/finding) from a freeform description of what happened. Internally rigorous (evidence inventory, claim-strength discipline, adversarial review), lean single-file HTML house style for output. Publish is opt-in.

• /jira:plan

  Plan the active sprint. jira-planner produces 01-PLAN.md, 02-PLAN.md per wave plus CONTEXT.md; jira-plan-checker audits all plans. Stall detection on revision. Optionally pushes a GitHub issue.

• /jira:research

  Start a sprint by researching it. Spawns parallel jira-researcher agents (codebase, patterns, external) and synthesizes findings into RESEARCH.md. Updates STATE.md.

• /jira:retro

  Generate a retrospective for the active sprint, a specific sprint, or a date range. Opt-in — never auto-fires.

• /jira:review

  Review the diff for the active sprint or a given branch/range. Spawns jira-reviewer; reports findings by severity. Does not fix.

• /jira:serve

  Build a static HTML review site from all sprints in .jira/sprints/ and serve it on a local port. Default serves every markdown file in every sprint; filter with --only. Extra markdown dirs (RFCs, specs) can be appended as sections with --include.

• /jira:triage

  Triage the active sprint's plans into independently-grabbable GitHub issues using vertical slices. Adapted from mattpocock's to-issues pattern. Uses caveman lite.

Subagents (9)

• jira-advisor

  Independent second-opinion agent that challenges triage recommendations or sprint plans. Reads the same artifacts as the planner/triager but approaches from a skeptical stance. Spawned by /jira:advisor.

• jira-executor

  Executes a single PLAN.md (one wave-plan) with atomic commits. Worktree-aware. Updates EXECUTION.md as it goes. Orchestrator spawns one executor per plan; multiple executors run in parallel within the same wave.

• jira-nyquist

  Validates that the executed sprint actually meets PLAN.md's Nyquist criteria. Fills coverage gaps by writing tests for any criterion not already covered. Implementation files are READ-ONLY. Spawned by /jira:execute after jira-executor finishes.

• jira-paper-reviewer

  Adversarial peer reviewer for a drafted engineering paper. Independent of the drafting process — challenges claim strength, evidence quality, and promotional language before publish. Returns a structured verdict for stall detection. Spawned by /jira:paper after the draft is written.

• jira-plan-checker

  Audits all *-PLAN.md files in a sprint by working backward from the goal. Verifies multi-source coverage matrix, per-plan task budget, parallel-safety, and CONTEXT.md decision implementation. Independent of jira-planner. Returns structured issue list for stall detection. Spawned by /jira:plan after

• jira-planner

  Reads BRIEF, RESEARCH, CONTEXT and produces one or more numbered PLAN files (01-PLAN.md, 02-PLAN.md, ...) grouped by execution wave. Each plan ≤ 3 tasks. Runs source-coverage audit and schema-push detection. Spawned by /jira:plan.

• jira-researcher

  One focus area of sprint research. Spawned in parallel with sibling researchers by /jira:research. Reads the sprint BRIEF, investigates a single dimension (codebase, patterns, or external), and returns a focused findings document with confidence-tiered sources.

• jira-reviewer

  Reviews the diff for the current sprint (or current branch) and reports issues by severity. Doesn't fix — only reports. Spawned by /jira:review.

• jira-verifier

  Goal-backward post-execution verifier. Asks "does the codebase as it stands now actually deliver the goal?" Distinct from jira-nyquist (test coverage) and jira-reviewer (diff audit). Spawned by /jira:execute after jira-nyquist passes.

Similar plugins