@ikunin/sprintpilot 2.2.31 → 2.3.1

package/_Sprintpilot/skills/sprintpilot-code-review/workflow.md

@@ -1,111 +0,0 @@
-# Multi-Agent Code Review
-
-## Purpose
-
-Perform a thorough code review using 3 parallel subagents, each with a different review lens. Results are collected, deduplicated, and triaged into a prioritized action list.
-
-## When to Use
-
-Use this instead of stock `bmad-code-review` when you want deeper coverage. The autopilot can be configured to call this automatically.
-
----
-
-## Step 1 — Gather Context
-
-<action>Identify the story being reviewed from sprint-status.yaml or user input.</action>
-<action>Generate the diff to review:
-```bash
-git diff origin/main...HEAD --unified=5
-```
-If the diff exceeds 3000 lines, summarize by file and only pass relevant sections to agents.
-Save full diff to `review-diff.txt` for agent reference.
-</action>
-<action>Read the story file to extract acceptance criteria.</action>
-<action>Set `{{diff_file}}` = path to review-diff.txt</action>
-<action>Set `{{story_file}}` = path to story file</action>
-
----
-
-## Step 2 — Launch 3 Review Agents in Parallel
-
-Launch ALL THREE agents in a **single message** using the Agent tool. Each agent gets its own inlined prompt (not a Skill reference).
-
-<critical>
-All 3 Agent calls MUST be in the same message to run in parallel.
-Each agent's result is capped at ~2000 tokens via structured output instructions.
-</critical>
-
-### Agent 1: Blind Hunter (Adversarial Review)
-
-```
-Agent(
-  description: "Blind adversarial code review",
-  prompt: <read from ./agents/blind-hunter.md, append diff content or diff_file path>
-)
-```
-
-### Agent 2: Edge Case Hunter
-
-```
-Agent(
-  description: "Edge case analysis",
-  prompt: <read from ./agents/edge-case-hunter.md, append diff content or diff_file path>
-)
-```
-
-### Agent 3: Acceptance Auditor
-
-```
-Agent(
-  description: "Acceptance criteria audit",
-  prompt: <read from ./agents/acceptance-auditor.md, append diff content + story file content>
-)
-```
-
----
-
-## Step 3 — Triage Results
-
-<action>Collect all 3 agent results.</action>
-
-<action>For each finding, classify:
-- **PATCH** — concrete code fix needed, actionable
-- **WARN** — valid concern but no code change needed (document for awareness)
-- **DISMISS** — false positive, not applicable, or already handled
-
-Deduplication rules:
-- Same file + same line range + same concern → merge into one finding
-- **Contradictory findings** (Agent A says "add check", Agent B says "remove check"):
-  → If Acceptance Auditor cites an AC → Acceptance Auditor wins
-  → Otherwise → classify as `decision_needed` and flag for user
-</action>
-
-<action>Produce the triage report:
-
-```markdown
-## Code Review — Triage Report
-
-### PATCH (apply these)
-1. **[P1]** {title} — {file}:{line} — {description} — Source: {agent}
-2. **[P2]** ...
-
-### WARN (acknowledge, no code change)
-1. **[W1]** {title} — {description} — Source: {agent}
-
-### DISMISSED
-1. **[D1]** {reason} — Source: {agent}
-
-### DECISION NEEDED (contradictory or ambiguous)
-1. **[DN1]** {description} — Agent A says: ... / Agent B says: ...
-```
-</action>
-
----
-
-## Step 4 — Output
-
-<action>Present the triage report to the caller (autopilot or user).</action>
-<action>If running under autopilot: the autopilot will auto-apply all PATCH findings and commit each one.</action>
-<action>If running manually: present findings and ask user which to apply.</action>
-
-<action>Suggest next step: "Apply patches, then run full test suite."</action>

package/_Sprintpilot/skills/sprintpilot-party-mode/SKILL.md

@@ -1,6 +0,0 @@
----
-name: sprintpilot-party-mode
-description: 'Real parallel multi-agent discussions. Select 2-3 BMad Method agent personas per round, launch them simultaneously with a topic, collect responses as a discussion round. Supports multiple rounds. Use when you need diverse perspectives from BMad personas (architect, PM, QA, etc.) debating in parallel rather than sequentially.'
----
-
-Follow the instructions in ./workflow.md.

package/_Sprintpilot/skills/sprintpilot-party-mode/workflow.md

@@ -1,138 +0,0 @@
-# Multi-Agent Party Mode
-
-## Purpose
-
-Run real parallel multi-persona discussions. Instead of sequentially role-playing each persona (as stock `bmad-party-mode` does), this launches 2-3 Agent subagents simultaneously, each embodying a different BMAD persona. Results are collected and presented as a discussion round.
-
----
-
-## Step 1 — Setup
-
-<action>Get from user or context:
-- **Topic/Question**: what to discuss
-- **Personas**: which BMAD personas to include (2-3 per round)
-  Available: analyst, architect, pm, dev, qa, ux-designer, tech-writer, sm
-- **Context files**: any project artifacts to provide as context (PRD, architecture, etc.)
-- **Rounds**: how many discussion rounds (default: 2)
-
-If not specified, recommend a relevant set based on the topic:
-- Architecture decisions → architect, dev, qa
-- Product direction → pm, analyst, ux-designer
-- Implementation approach → dev, architect, qa
-- Process/workflow → sm, pm, dev
-</action>
-
----
-
-## Step 2 — Load Persona Definitions
-
-<action>For each selected persona, read the agent definition from BMAD:
-- `{project-root}/_bmad/_config/agents/` — look for persona YAML files
-- Or look in the installed skills directory for `bmad-agent-{persona}/SKILL.md`
-
-Extract the persona's:
-- Role description
-- Expertise areas
-- Communication style
-- Key concerns/priorities
-</action>
-
----
-
-## Step 3 — Run Discussion Rounds
-
-For each round (1 to {{num_rounds}}):
-
-<critical>Launch ALL persona agents for this round in a single message.</critical>
-
-For each persona in this round:
-```
-Agent(
-  description: "{persona_name} perspective on {topic}",
-  prompt: "You are the {persona_name} on a BMAD development team.
-
-  ## Your Role
-  {persona_description}
-
-  ## Your Priorities
-  {persona_priorities}
-
-  ## Discussion Topic
-  {topic}
-
-  ## Context
-  {project_context_files_content}
-
-  ## Previous Round Discussion
-  {previous_round_responses — empty for round 1}
-
-  ## Instructions
-
-  Respond to the topic from your persona's perspective.
-  - State your position clearly
-  - Raise concerns specific to your role
-  - Propose concrete actions
-  - If responding to previous round: agree, disagree, or build on other personas' points
-  - Be direct and specific, not generic
-
-  Cap response at 1000 tokens."
-)
-```
-
-<action>Collect all responses for this round.</action>
-
-<action>Present the round:
-
-```markdown
-## Round {{round_number}}
-
-### {Persona 1 Name} ({role})
-{response}
-
-### {Persona 2 Name} ({role})
-{response}
-
-### {Persona 3 Name} ({role})
-{response}
-```
-</action>
-
-<action>For subsequent rounds, include previous round responses as context so personas can respond to each other.</action>
-
----
-
-## Step 4 — Synthesis
-
-After all rounds complete:
-
-<action>Produce a synthesis:
-
-```markdown
-## Discussion Summary
-
-### Topic
-{topic}
-
-### Participants
-{persona list with roles}
-
-### Points of Agreement
-- ...
-
-### Points of Disagreement
-- {persona A} vs {persona B}: ...
-  Resolution suggestion: ...
-
-### Action Items
-1. [Owner: {persona}] {action}
-2. ...
-
-### Open Questions
-- ...
-
-### Recommendation
-[Based on the discussion, what is the recommended path forward?]
-```
-</action>
-
-<action>Ask user: "Continue with another topic, or apply these insights to the current workflow?"</action>