You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You MUST follow this structured workflow to create a comprehensive feature specification using multiple agent perspectives.
307
+
308
+
## Step 1: PM-Led Initial Outline
309
+
310
+
Invoke Parker (Product Manager) to create an initial RFE outline based on rfe.md (or if that doesn't exist, use these requirements: ${workflow.description}).
311
+
312
+
Parker should create an outline containing:
313
+
- Executive summary with business justification and market analysis
314
+
- Business impact and customer requirements
315
+
- Technical approach (high-level, no implementation details)
316
+
- User experience considerations
317
+
- Implementation scope (in-scope vs out-of-scope)
318
+
- Acceptance criteria
319
+
- Risks and mitigation strategies
320
+
- Success metrics
321
+
322
+
## Step 2: Agent Selection
323
+
324
+
Parker should analyze the feature type and select TWO agents best suited to review the outline:
325
+
326
+
**Selection criteria by feature type**:
327
+
- Infrastructure/Platform features → Archie (Architect) + Stella (Staff Engineer)
328
+
- User-facing UI features → Felix (UX Feature Lead) + Stella (Staff Engineer)
329
+
- API/Integration features → Archie (Architect) + Taylor (Team Member)
330
+
- Documentation features → Terry (Technical Writer) + Casey (Content Strategist)
331
+
- Testing/Quality features → Neil (Test Engineer) + Stella (Staff Engineer)
332
+
333
+
## Step 3: Parallel Agent Reviews
334
+
335
+
Launch BOTH selected agents in parallel (single message with multiple Task tool calls) to review Parker's outline.
336
+
337
+
Each agent should:
338
+
- Review from their domain expertise perspective
339
+
- Provide structured feedback with specific recommendations
340
+
- Identify gaps, risks, architectural concerns, and improvement opportunities
341
+
342
+
## Step 4: Document Versioning
343
+
344
+
Save all versions during the refinement process:
345
+
1. Save Parker's initial outline as \`specs/[feature-dir]/outline-v1-pm-initial.md\`
346
+
2. Save Agent 1's feedback as \`specs/[feature-dir]/feedback-agent1.md\`
347
+
3. Save Agent 2's feedback as \`specs/[feature-dir]/feedback-agent2.md\`
348
+
4. Save Parker's revised outline as \`specs/[feature-dir]/outline-v2-revised.md\`
349
+
350
+
## Step 5: Final Spec Generation
351
+
352
+
Have Parker incorporate all feedback and then run:
353
+
\`/specify Develop a new feature based on the revised outline\`
354
+
355
+
This will generate the final spec.md using the collaborative outline as the foundation.
0 commit comments