Team support intake and automatic status tracking
Team members hit issues and post in chat. Messages scroll away. Nobody files a ticket. The problem festers.
End-of-day status updates mean context-switching to recall what you did, then typing it all out again.
Great work happens every day but nobody has time to write it up. Learnings stay siloed.
Every Amplifier session knows what you worked on, what went wrong, and what you accomplished. Instead of asking people to report — capture it automatically from the work itself.
“ What if support requests, status updates, and story submissions were as easy as saying help me, or happened with no effort at all? ”
Describe your problem in natural language. The bundle extracts structured details, checks for duplicates, and files a GitHub issue — in seconds.
An opt-in hook summarizes your session automatically at turn thresholds, git events, and session end. Your status page stays current without lifting a finger.
Generate a polished presentation from your session and submit a PR to the stories repo. Ship your wins while the context is fresh.
# User just says what's wrong
"I can't get the shadow environment to install my local core changes"
# Bundle runs the pipeline:
extract-issue-quick → structured title, body, labels
find-duplicates → checks existing issues
file-issue → creates GitHub issue with full contextTwo extraction modes: extract-issue-quick for speed, extract-issue-full for detailed triage with environment and reproduction steps.
Multi-trigger design: fires at configurable turn count (default 10), on git commits/pushes, and at session end.
Team status is off by default — opt in via ~/.amplifier/team-tracking.yaml.
# ~/.amplifier/team-tracking.yaml
enabled: true # opt-in required
throttle: "4h" # minimum time between updates
detail_level: "summary" # summary | detailed | minimal
exclude: # paths to never include
- "personal/*"
- "private-notes/*"Set minimum intervals between status updates to avoid noise.
Ensure sensitive directories are never included in summaries.
Choose how much context appears — from minimal to full detail.
Turn any session into a polished presentation and submit it to the Amplifier Stories repo — all from your working session.
The storyteller agent creates an HTML presentation from your session context.
Preview the deck locally, iterate on content and narrative arc.
The submit-story-pr recipe creates a branch and opens a pull request automatically.
7 recipes, 1 behavior, 1 module — everything wired together.
| Component | Type | Purpose |
|---|---|---|
| check-gh | Recipe | Verify GitHub CLI authentication |
| extract-issue-full | Recipe | Detailed issue extraction with triage |
| extract-issue-quick | Recipe | Fast structured issue extraction |
| file-issue | Recipe | Create GitHub issue from extracted data |
| find-duplicates | Recipe | Search existing issues for duplicates |
| submit-story-pr | Recipe | Submit story deck via pull request |
| update-team-status | Recipe | Push status update to team page |
| team-status | Behavior | Opt-in session summarization behavior |
| hook-team-status | Module | Multi-trigger hook (turns, git, session end) |
Timeline: Jan 14 – Feb 9, 2026 · Primary author: Salil Das
Data as of February 20, 2026 · Feature status: Active v1.3.0
Install the MADE Support Bundle and let your sessions do the reporting.
Part of the Amplifier ecosystem · Built by the MADE team