fix: add OPERATIONS session type for PM/planning sessions (#2914)#2923
Merged
fix: add OPERATIONS session type for PM/planning sessions (#2914)#2923
Conversation
Power-steering incorrectly activated dev checks on Q&A/PM sessions (e.g. /pm-architect) because Read/Grep tool usage triggered INVESTIGATION classification, which applies workflow checks. Add OPERATIONS session type detected via PM/planning keywords (prioritize, backlog, roadmap, sprint, triage, etc.) that skips all power-steering considerations — same as SIMPLE sessions. Detection priority: SIMPLE > OPERATIONS > DEVELOPMENT > INVESTIGATION. Closes #2914, Closes #2913 Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Contributor
|
🤖 Auto-fixed version bump The version in If you need a minor or major version bump instead, please update |
Contributor
Repo Guardian - PassedAll changed files have been reviewed:
No ephemeral content detected. All files are durable and appropriate for the repository.
|
12 unit tests covering: - PM/planning keyword detection (pm-architect, backlog, roadmap, sprint) - OPERATIONS skips all considerations - Env override AMPLIHACK_SESSION_TYPE=OPERATIONS - Priority: SIMPLE > OPERATIONS > DEVELOPMENT > INVESTIGATION - Code modifications with operations keywords Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
8 tests covering both Claude and Copilot sessions: - Claude /pm-architect → OPERATIONS classification - Claude full check() flow → approve (no blocks) - Copilot backlog triage → OPERATIONS classification - Copilot full check() flow → approve (no blocks) - Development sessions still get full checks - Simulates real transcript structure with tool_use blocks Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Contributor
Repo Guardian - PassedAll changed files have been reviewed: Files Changed (8 total)
AssessmentNo ephemeral content detected. All files are:
The changes add a permanent feature to classify PM/planning sessions as OPERATIONS type and skip development workflow checks. This is proper feature development, not temporary content.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Root Cause
Power-steering incorrectly activated dev workflow checks on PM sessions (e.g.
/pm-architect) because heavy Read/Grep tool usage triggered INVESTIGATION classification, which appliesworkflow_invocation,next_steps, anddocumentation_updateschecks that are irrelevant for planning sessions.Changes
session_detection.py: AddOPERATIONS_KEYWORDSlist, detect before tool usage analysisconsiderations.yaml: Document OPERATIONS session type in header.claude/andamplifier-bundle/copies syncedCloses #2914, Closes #2913
Test plan
/pm-architectand verify no power-steering dev checks fireAMPLIHACK_SESSION_TYPE=OPERATIONSworksGenerated with Claude Code