john/claude-engineering-plugin
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(agents): remove self-referencing example blocks that cause recursive self-invocation (#496)

Browse Source 
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
Trevin Chow
2026-04-03 01:40:34 -07:00
committed by GitHub
parent 6dcb4a3c55
commit 2c90aebe3b
24 changed files with 0 additions and 447 deletions
Download Patch File Download Diff File Expand all files Collapse all files

21
plugins/compound-engineering/agents/workflow/spec-flow-analyzer.md
View File

@@ -4,27 +4,6 @@ description: "Analyzes specifications and feature descriptions for user flow com
model: inherit
---
<examples>
<example>
Context: The user has just finished drafting a specification for OAuth implementation.
user: "Here's the OAuth spec for our new integration: [OAuth spec details]"
assistant: "Let me use the spec-flow-analyzer agent to analyze this OAuth specification for user flows and missing elements."
<commentary>Since the user has provided a specification document, use the Task tool to launch the spec-flow-analyzer agent to identify all user flows, edge cases, and missing clarifications.</commentary>
</example>
<example>
Context: The user is planning a new social sharing feature.
user: "I'm thinking we should add social sharing to posts. Users can share to Twitter, Facebook, and LinkedIn."
assistant: "This sounds like a feature specification that would benefit from flow analysis. Let me use the spec-flow-analyzer agent to map out all the user flows and identify any missing pieces."
<commentary>The user is describing a new feature. Use the spec-flow-analyzer agent to analyze the feature from the user's perspective, identify all permutations, and surface questions about missing elements.</commentary>
</example>
<example>
Context: The user has created a plan for a new onboarding flow.
user: "Can you review this onboarding plan and make sure we haven't missed anything?"
assistant: "I'll use the spec-flow-analyzer agent to thoroughly analyze this onboarding plan from the user's perspective."
<commentary>The user is explicitly asking for review of a plan. Use the spec-flow-analyzer agent to identify all user flows, edge cases, and gaps in the specification.</commentary>
</example>
</examples>
Analyze specifications, plans, and feature descriptions from the end user's perspective. The goal is to surface missing flows, ambiguous requirements, and unspecified edge cases before implementation begins -- when they are cheapest to fix.
## Phase 1: Ground in the Codebase