shotgun-sh 0.4.3.dev1__tar.gz → 0.4.3.dev2__tar.gz

{shotgun_sh-0.4.3.dev1 → shotgun_sh-0.4.3.dev2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: shotgun-sh
-Version: 0.4.3.dev1
+Version: 0.4.3.dev2
 Summary: AI-powered research, planning, and task management CLI tool
 Project-URL: Homepage, https://shotgun.sh/
 Project-URL: Repository, https://github.com/shotgun-sh/shotgun

{shotgun_sh-0.4.3.dev1 → shotgun_sh-0.4.3.dev2}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "shotgun-sh"
-version = "0.4.3.dev1"
+version = "0.4.3.dev2"
 description = "AI-powered research, planning, and task management CLI tool"
 readme = "README.md"
 license = { text = "MIT" }

{shotgun_sh-0.4.3.dev1 → shotgun_sh-0.4.3.dev2}/src/shotgun/prompts/agents/router.j2

@@ -178,7 +178,7 @@ You: "What specifically would you like to update in the specification?
 
 <GOOD_EXAMPLE name="Clear request - create plan">
 User: "Add OAuth2 authentication to the spec with Google and GitHub providers"
-You: *calls create_plan with goal="Add OAuth2 to specification" and steps=["Add OAuth2 section with Google/GitHub providers"]*
+You: *calls create_plan with goal="Add OAuth2 to specification" and steps=["Research existing auth patterns in codebase", "Write OAuth2 specification with Google/GitHub providers"]*
 "Here's my plan: [shows plan]. Ready to proceed?"
 </GOOD_EXAMPLE>
 
@@ -309,14 +309,30 @@ Do not create a plan for:
 </PLAN_MANAGEMENT>
 
 <PIPELINE_ORDER>
-When working on a new feature or project, follow this order:
+When creating a plan for a new feature or integration, include steps in this order:
 
-1. Research first using delegate_to_research
-2. Specification second using delegate_to_specification
-3. Plan third using delegate_to_plan
-4. Tasks last using delegate_to_tasks
+1. Research existing codebase patterns first (delegate_to_research)
+2. Write specification second (delegate_to_specification)
+3. Create implementation plan third (delegate_to_plan)
+4. Generate tasks last (delegate_to_tasks)
 
-This order ensures each stage has context from previous stages.
+This order ensures each stage has context from previous stages. The research step is critical - you cannot write a good spec without understanding the existing codebase architecture.
+
+<BAD_EXAMPLE name="Plan skips research">
+Goal: "Add WebSocket support"
+Steps:
+1. Write specification for WebSocket integration
+2. Create implementation plan
+WRONG - skipped research. How can you spec an integration without understanding the existing code?
+</BAD_EXAMPLE>
+
+<GOOD_EXAMPLE name="Plan starts with research">
+Goal: "Add WebSocket support"
+Steps:
+1. Research existing real-time/connection patterns in codebase
+2. Write specification for WebSocket integration
+3. Create implementation plan
+</GOOD_EXAMPLE>
 
 Be minimal:
 - Do the minimum research necessary - don't over-research