Human-tagged feature work in GitHub Issues
A workflow where a single labeler triggers agent creation for feature requests, excluding themselves from assignment.
This pattern is useful when a PM or tech lead triages incoming requests and decides which ones are ready for an agent to pick up.
What it does
- Watches the
acme/apprepository - Triggers when an issue is labeled
agent-readyandfeature - Excludes the PM (
@pm-alice) from assignment — they labeled it, they don't implement it - Uses a
feature-workspacewith broader context and planning instructions - Moves the issue to
in-reviewwhen done - Does not terminate on leave — the agent stays alive to handle review feedback
Issue tracker
text
Settings -> Workspaces -> feature-workspace -> Issue Trackers
Add GitHub Issues:
token: ${GITHUB_TOKEN}
webhook secret: ${GITHUB_WEBHOOK_SECRET}Workflow: feature-bot
yaml
# .elasticclaw/workflows/feature-bot.yaml
schema_version: v1
name: feature-bot
trigger:
github_issues:
event: issue_labeled
repositories:
- acme/app
states:
- open
labels:
- agent-ready
- feature
tags: [feature]
stages:
- id: working
label: Working
entry: true
on_enter:
inject: |
Read CONTEXT.md, plan the feature, implement it, and open a PR.
- id: pr_opened
label: PR Opened
triggers:
- message_contains: "[DONE]"
on_enter:
add_labels: [in-review]
- id: merged
label: Merged
triggers:
- pr_merged: {}
terminal: trueThe labeling workflow
- User opens a feature request issue in
acme/app - PM reviews it, adds labels
agent-ready+feature - Workflow webhook fires — labels match, issue is open → agent spawned
- Agent implements the feature, opens a PR, sends
[DONE] - Issue moved to
in-review, agent watches for CI/review comments - PM removes
agent-readylabel → agent stays alive (terminate_on_leave: false) - PR merges → agent terminates automatically
Workspace: feature-workspace
A workspace with planning instructions and broader context for feature work.
yaml
# .elasticclaw/workspaces/feature-workspace/elasticclaw-config.yaml
name: feature-workspace
provider: daytona
llm_key: fireworks-kimi
default_model: fireworks/accounts/fireworks/models/kimi-k2p6
repositories:
- repo: acme/app
permissions: write
tags: [feature]markdown
# .elasticclaw/workspaces/feature-workspace/AGENTS.md
You are a feature implementation agent. Read CONTEXT.md, propose a plan,
then implement. Open a PR and send [DONE] <pr-url> when ready.GitHub webhook setup
- Go to repo → Settings → Webhooks → Add webhook
- Payload URL:
https://server.example.com/api/workspaces/feature-workspace/webhooks/github-issues - Content type:
application/json - Secret: the webhook secret from workspace issue tracker settings
- Events: Issues