Deprecate issue-creator agent + change spawn hook to require issue reference #57
Labels
No labels
domain:backend
domain:devops
domain:frontend
status:approved
status:in-progress
status:needs-fix
status:qa
type:bug
type:devops
type:feature
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
ldraney/claude-custom#57
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Plan
plan-2026-02-26-tf-modularize-postgres-- Phase 7f-1 (subphase of 7f Doc Cleanup + SOP Hardening)Repo
forgejo_admin/claude-customUser Story
As Betty Sue (main session agent)
I want the agent spawn hook to require a Forgejo issue reference instead of a plan reference
So that every spawned agent traces to a specific issue and undirected agent spawns are blocked
Context
The
check-agent-spawn.shhook currently requiresplan-*orproject-*in agent prompts. This was the right guard initially, but now that issues are the unit of work (issue-as-spec), the gate should be an issue reference.The
issue-creatoragent type is also being removed. Betty Sue creates issues directly viamcp__forgejo__create_issue. Issue scoping is a planning conversation between Betty Sue and Lucas — not something to delegate to an agent.Dottie (general-purpose doc ops) is the exception — her work isn't tied to Forgejo issues. She uses plan references.
Current hook logic (line 17):
if echo "$PROMPT" | grep -qE 'plan-|project-'; thenNew logic should be:
#[0-9]+,issue,Issue,Forgejo issue) → allowplan-) AND subagent_type isgeneral-purpose→ allow (Dottie exception)The subagent_type can be read from the tool input:
jq -r '.tool_input.subagent_type // empty'File Targets
Files the agent should modify:
hooks/check-agent-spawn.sh-- change grep fromplan-|project-to issue reference check with Dottie exceptionsettings.json-- removeissue-creatorfrom agent typeshooks/inject-subagent-context.sh-- remove issue-creator caseagents/betty-sue.md-- remove issue-creator referencesFiles the agent should delete:
agents/issue-creator.md-- the agent definition being removedFiles the agent should NOT touch:
agents/dev.md,agents/qa.md-- no changes neededskills/create-issue/SKILL.md-- keep the skill, Betty Sue uses it inlineAlso clean up:
.claude/worktrees/agent-a27bc6af/-- stale worktree, delete.claude/worktrees/agent-acda354e/-- stale worktree, delete.claude/worktrees/agent-a6ee25b5/-- stale worktree, deleteAcceptance Criteria
issue-creatoragent type fully removed (agent def, settings, inject hook)check-agent-spawn.shrequires issue reference for dev/QA/Explore agentscheck-agent-spawn.shallows plan reference for general-purpose agents (Dottie)"Fix issue #100 on repo. Plan: plan-foo"passes the hook"Update docs. Plan: plan-foo"passes the hook"Explore the codebase"is deniedbetty-sue.mdno longer references issue-creatorTest Expectations
echo '{"tool_input":{"prompt":"Fix issue #100","subagent_type":"dev"}}' | bash hooks/check-agent-spawn.sh(should exit 0)Constraints
create-issueSKILL.md — Betty Sue uses it inline, not via agentChecklist
Related
phase-7f-1-deprecate-issue-creator-- phase noteagent-spawn-conventions-- convention to update after mergeagent-workflow-- references agent types