britt/chat
Skills for chat agents rather than coding agents: writing and communication, research, diagrams, requirements, specs, and daily planning - no repository, git, or gh CLI required
Use when the user asks for an architecture diagram, says 'show me the system architecture' or 'diagram the components', or during project planning - generates GitHub-compatible Mermaid flowcharts showing components, layers, subgraph boundaries, and data flows
Use when asked 'what am I missing?', reviewing an issue or draft before submission, or checking documentation completeness - detects requirement, spec, and doc gaps and generates prioritized actionable questions
Use when the user asks to plan their day with phrases like "plan the day", "plan my day", "plan today", or similar variations, or wants a morning check-in on how to spend the day across work and the rest of their life.
Use when writing or refining a GitHub issue, epic, or other work item that needs a size, when asked to estimate, point, or size work, or when deciding whether an item is an issue or an epic - gives an issue one story-point estimate on a powers-of-two scale (1, 2, 4, 8) and an epic the sum of its children's points, with no upper limit, recorded as a label, an Estimate section, and a project field
Use when the user says 'create issues for...', 'break this into tasks', or 'decompose this feature', or when converting a project description into GitHub issues - produces 5-15 INVEST-quality issues with user stories, acceptance criteria, dependencies, labels, and powers-of-two point estimates
Use when writing PR descriptions, issue bodies, documentation, or notes - applies consistent Markdown conventions (heading levels, list markers, code-block languages, link text) and provides PR and issue templates
Use when creating any Mermaid diagram (flowchart, sequence, class, state, ER, Gantt) in markdown, or when a diagram fails to render on GitHub - covers the syntax rules that break GitHub rendering (parentheses in labels, mismatched brackets) plus per-type examples
Use when gathering project requirements, or when a user says 'help me define requirements' or 'figure out what to build' - adaptive wizard covering functional, nonfunctional, constraints, and edge cases with domain-specific questions for web apps, APIs, CLIs, mobile, and data pipelines
Use when asked to research a technology, library, or concept via web search, compare options (X vs Y), or gather background for a decision - synthesizes findings into a cited summary with comparison tables, screenshots of key visuals, and a recommendation
Use when writing status updates, communicating delays or blockers, announcing launches, or requesting decisions and resources from stakeholders - structures the message by audience level (exec/management/peer/team) with lead-with-the-punchline framing
Use when catching up on a long GitHub issue or PR discussion thread, or asked to summarize a thread, extract key decisions, or list action items - produces a structured summary with TL;DR, decisions, action items, open questions, and next steps
Use when asked to write a product spec, PRD, or requirements document, or to design a new feature or project before implementation - interactively elicits problem, audience, success criteria, and scope, then produces a structured spec file
Use when asked to write user stories, define requirements, break a feature into stories, or draft product/feature issues - produces stories in "As a [persona], I want [action], so that [benefit]" format with Given-When-Then acceptance criteria and an INVEST quality checklist