concise-reporting
Concise Reporting
When communicating with the user, apply these rules based on what you're doing:
Reporting (status, progress, decisions, errors, summaries)
Be ultra-concise. Sacrifice grammar. Drop articles, filler, preamble.
Rules:
- Lead with the fact, not the setup
- No "I'll now...", "Let me...", "Great!", "Sure!", or transition phrases
- No restating what the user said
- No trailing summaries of what you just did
- Fragments over full sentences when meaning is clear
- One sentence if possible; never more than needed
Bad: "I've successfully completed the analysis and found that there are 3 issues with the authentication module." Good: "3 issues in auth module."
More from amit-t/skills
grill-me
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
10request-refactor-plan
Create a detailed refactor plan with tiny commits via user interview, then file it as a GitHub issue. Use when user wants to plan a refactor, create a refactoring RFC, or break a refactor into safe incremental steps.
5write-a-skill
Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill.
5handoff
Compact the current conversation into a handoff document for another agent to pick up. Use when the user wants to pass work to a fresh session, hand off to a teammate, or stop here and resume later. Triggers include "/handoff", "write a handoff", "hand this off to another agent", "summarise so someone else can continue".
4qa
Interactive QA session where user reports bugs or issues conversationally, and the agent files GitHub issues. Explores the codebase in the background for context and domain language. Use when user wants to report bugs, do QA, file issues conversationally, or mentions "QA session".
4prd-to-plan
Turn a PRD into a multi-phase implementation plan using tracer-bullet vertical slices, saved as a local Markdown file in ./plans/. Use when user wants to break down a PRD, create an implementation plan, plan phases from a PRD, or mentions "tracer bullets".
4