rpi-kit 1.4.0 → 2.0.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (53) hide show
  1. package/.claude-plugin/marketplace.json +9 -6
  2. package/.claude-plugin/plugin.json +4 -4
  3. package/AGENTS.md +2016 -117
  4. package/CHANGELOG.md +83 -0
  5. package/README.md +116 -169
  6. package/agents/atlas.md +61 -0
  7. package/agents/clara.md +49 -0
  8. package/agents/forge.md +38 -0
  9. package/agents/hawk.md +54 -0
  10. package/agents/luna.md +50 -0
  11. package/agents/mestre.md +61 -0
  12. package/agents/nexus.md +63 -0
  13. package/agents/pixel.md +48 -0
  14. package/agents/quill.md +40 -0
  15. package/agents/razor.md +41 -0
  16. package/agents/sage.md +52 -0
  17. package/agents/scout.md +49 -0
  18. package/agents/shield.md +51 -0
  19. package/bin/cli.js +160 -53
  20. package/bin/onboarding.js +46 -28
  21. package/commands/rpi/archive.md +149 -0
  22. package/commands/rpi/docs.md +106 -168
  23. package/commands/rpi/implement.md +163 -401
  24. package/commands/rpi/init.md +150 -67
  25. package/commands/rpi/learn.md +114 -0
  26. package/commands/rpi/new.md +85 -155
  27. package/commands/rpi/onboarding.md +157 -336
  28. package/commands/rpi/party.md +212 -0
  29. package/commands/rpi/plan.md +241 -205
  30. package/commands/rpi/research.md +162 -104
  31. package/commands/rpi/review.md +350 -104
  32. package/commands/rpi/rpi.md +125 -0
  33. package/commands/rpi/simplify.md +156 -93
  34. package/commands/rpi/status.md +91 -114
  35. package/package.json +7 -3
  36. package/skills/rpi-agents/SKILL.md +63 -39
  37. package/skills/rpi-workflow/SKILL.md +160 -186
  38. package/agents/code-reviewer.md +0 -108
  39. package/agents/code-simplifier.md +0 -82
  40. package/agents/cto-advisor.md +0 -61
  41. package/agents/doc-synthesizer.md +0 -67
  42. package/agents/doc-writer.md +0 -37
  43. package/agents/explore-codebase.md +0 -88
  44. package/agents/plan-executor.md +0 -95
  45. package/agents/product-manager.md +0 -59
  46. package/agents/requirement-parser.md +0 -51
  47. package/agents/senior-engineer.md +0 -61
  48. package/agents/test-engineer.md +0 -23
  49. package/agents/ux-designer.md +0 -58
  50. package/codex.md +0 -72
  51. package/commands/rpi/add-todo.md +0 -83
  52. package/commands/rpi/set-profile.md +0 -124
  53. package/commands/rpi/test.md +0 -198
@@ -0,0 +1,212 @@
1
+ ---
2
+ name: rpi:party
3
+ description: Multi-agent debate on any topic. Nexus facilitates, 3-5 agents discuss.
4
+ argument-hint: "[feature-name] \"topic to debate\""
5
+ allowed-tools:
6
+ - Read
7
+ - Glob
8
+ - Grep
9
+ - Agent
10
+ - AskUserQuestion
11
+ ---
12
+
13
+ # /rpi:party — Party Mode
14
+
15
+ Multi-agent debate facilitated by Nexus. Select 3-5 agents based on the topic, let them argue their perspectives, then synthesize a recommendation with trade-offs.
16
+
17
+ ---
18
+
19
+ ## Step 1: Load config
20
+
21
+ Read `.rpi.yaml` from the project root. Extract:
22
+ - `folder` (default: `rpi/features`)
23
+ - `solutions_dir` (default: `rpi/solutions`)
24
+ - `context_file` (default: `rpi/context.md`)
25
+ - `party_default_agents` (default: `4`)
26
+
27
+ If `.rpi.yaml` doesn't exist, use defaults silently.
28
+
29
+ ## Step 2: Parse arguments
30
+
31
+ Parse `$ARGUMENTS` to extract:
32
+ - Optional `{slug}` — a feature name (first word, if it doesn't start with `"`)
33
+ - `{topic}` — the debate topic (quoted string, or everything after the slug)
34
+
35
+ If no topic is provided, ask the user with AskUserQuestion:
36
+ "What topic do you want to debate? (e.g. 'GraphQL vs REST for the API?', 'how to handle token refresh?')"
37
+
38
+ ## Step 3: Gather feature context (if slug provided)
39
+
40
+ If a feature slug was provided:
41
+ 1. Check if `rpi/features/{slug}/` exists. If not:
42
+ ```
43
+ Feature '{slug}' not found. Proceeding without feature context.
44
+ ```
45
+ Clear the slug and continue.
46
+ 2. If it exists, read available artifacts — store as `$FEATURE_CONTEXT`:
47
+ - `rpi/features/{slug}/REQUEST.md` if it exists
48
+ - `rpi/features/{slug}/research/RESEARCH.md` if it exists
49
+ - `rpi/features/{slug}/plan/PLAN.md` if it exists
50
+
51
+ Read `rpi/context.md` (project context) if it exists — store as `$PROJECT_CONTEXT`.
52
+
53
+ ## Step 4: Nexus selects agents
54
+
55
+ Use the Agent tool to launch Nexus for agent selection:
56
+
57
+ ```
58
+ You are Nexus. Analyze the following debate topic and select 3-5 agents to participate.
59
+
60
+ ## Topic
61
+ {topic}
62
+
63
+ ## Feature Context
64
+ {$FEATURE_CONTEXT or "No feature context."}
65
+
66
+ ## Project Context
67
+ {$PROJECT_CONTEXT or "No project context."}
68
+
69
+ Select agents based on the topic category:
70
+
71
+ - Technical topics (architecture, implementation, patterns, performance) → Mestre + Atlas + Scout
72
+ - Product topics (UX, requirements, scope, user experience) → Clara + Luna + Pixel
73
+ - Security topics (auth, data protection, vulnerabilities, compliance) → Shield + Hawk + Mestre
74
+ - Mixed topics (trade-offs, strategy, cross-cutting concerns) → Mestre + Clara + Atlas + Shield
75
+
76
+ You may adjust the selection if the topic warrants it. Always pick 3-5 agents. For each selected agent, provide a one-line reason why they're relevant.
77
+
78
+ Output format:
79
+ ## Selected Agents
80
+ 1. {AgentName} — {reason}
81
+ 2. {AgentName} — {reason}
82
+ ...
83
+
84
+ ## Category
85
+ {Technical | Product | Security | Mixed}
86
+ ```
87
+
88
+ Store the output as `$NEXUS_SELECTION`. Parse the selected agent names from it.
89
+
90
+ ## Step 5: Launch debate agents in parallel
91
+
92
+ Use the Agent tool to launch all selected agents simultaneously. Each agent receives this prompt (adapted to their persona):
93
+
94
+ ```
95
+ You are {AgentName}. You've been called into a Party Mode debate.
96
+
97
+ ## Topic
98
+ {topic}
99
+
100
+ ## Feature Context
101
+ {$FEATURE_CONTEXT or "No feature context."}
102
+
103
+ ## Project Context
104
+ {$PROJECT_CONTEXT or "No project context."}
105
+
106
+ Share your perspective on this topic IN CHARACTER. Be opinionated and specific:
107
+ 1. State your position clearly — what do you recommend and why?
108
+ 2. Identify trade-offs and risks from your area of expertise
109
+ 3. If you disagree with an obvious counter-argument, preemptively address it
110
+ 4. Provide concrete examples or references where possible
111
+
112
+ Keep your response focused and under 500 words.
113
+
114
+ Output format:
115
+ ## {AgentName}'s Perspective
116
+ {your position and arguments}
117
+
118
+ ### Trade-offs
119
+ - {trade-off 1}
120
+ - {trade-off 2}
121
+
122
+ ### Recommendation
123
+ {your specific recommendation in 1-2 sentences}
124
+ ```
125
+
126
+ Store each agent's output as `$AGENT_{NAME}_OUTPUT`.
127
+
128
+ ## Step 6: Nexus synthesizes debate
129
+
130
+ Launch Nexus agent to produce the final synthesis:
131
+
132
+ ```
133
+ You are Nexus. Synthesize the Party Mode debate on: {topic}
134
+
135
+ ## Agent Perspectives
136
+ {all $AGENT_{NAME}_OUTPUT concatenated}
137
+
138
+ ## Feature Context
139
+ {$FEATURE_CONTEXT or "No feature context."}
140
+
141
+ Your task:
142
+ 1. Identify points of CONSENSUS — where agents agree
143
+ 2. Identify points of DISAGREEMENT — where agents conflict
144
+ 3. For each disagreement, evaluate the strength of each position
145
+ 4. Produce a clear recommendation with trade-offs
146
+ 5. Note any open questions that the team should resolve
147
+
148
+ Output format:
149
+ # Party Mode: {topic}
150
+
151
+ ## Participants
152
+ {list of agents and their roles}
153
+
154
+ ## Consensus
155
+ {points where agents agree}
156
+
157
+ ## Disagreements
158
+ {for each: what each side argues, strength of evidence, resolution}
159
+
160
+ ## Recommendation
161
+ {clear recommendation with reasoning}
162
+
163
+ ## Trade-offs
164
+ {key trade-offs to be aware of}
165
+
166
+ ## Open Questions
167
+ {unresolved items, if any}
168
+ ```
169
+
170
+ Store the output as `$NEXUS_SYNTHESIS`.
171
+
172
+ ## Step 7: Present results
173
+
174
+ Output the full `$NEXUS_SYNTHESIS` to the user.
175
+
176
+ ## Step 8: Offer to save decision
177
+
178
+ Ask the user with AskUserQuestion:
179
+ "Save this decision to rpi/solutions/decisions/? (y/n)"
180
+
181
+ ### If yes:
182
+
183
+ 1. Derive a slug from the topic (kebab-case, max 50 chars).
184
+ 2. Ensure directory exists: `rpi/solutions/decisions/`
185
+ 3. Write to `rpi/solutions/decisions/{topic-slug}.md`:
186
+ ```markdown
187
+ # {Topic}
188
+
189
+ ## Decision
190
+ {recommendation from Nexus synthesis}
191
+
192
+ ## Context
193
+ {summary of the debate — consensus, disagreements, trade-offs}
194
+
195
+ ## Participants
196
+ {list of agents involved}
197
+
198
+ ## Date
199
+ {YYYY-MM-DD}
200
+ ```
201
+
202
+ 4. Output:
203
+ ```
204
+ Decision saved: rpi/solutions/decisions/{topic-slug}.md
205
+ ```
206
+
207
+ ### If no:
208
+
209
+ Output:
210
+ ```
211
+ Decision not saved. You can revisit this topic anytime with /rpi:party.
212
+ ```