agent-crews

Write Architecture Decision Records when making significant technical choices. Use when selecting tools, patterns, frameworks, or making structural changes that future developers need to understand.

Write AGENTS.md files that serve as operating contracts for AI agents. Use when creating or updating AGENTS.md for a project. Trigger terms: AGENTS.md, agent instructions, agent contract, agent configuration, coding agent setup.

Quality rules for changelog entries. Use when validating, writing, or reviewing changelog content to ensure user-facing value communication.

Task completion sequence including verification, git, signaling, and handoff. Use when finishing a task or reporting status.

Architecture diagrams for documentation. Covers ASCII, Mermaid, C4, and D2. Applies C4 methodology by default. Trigger terms: diagram, flowchart, architecture diagram, sequence diagram, C4, mermaid, ascii diagram.

Classify documentation by audience and content type. Use when planning, auditing, or placing project documentation.

Audit project documentation for quality, completeness, and freshness. Use when assessing documentation health, planning cleanup, or measuring improvement.

Markup language selection for documentation. Covers Markdown, AsciiDoc, reStructuredText, and Typst. Trigger terms: asciidoc, restructuredtext, rst, typst, document format, multi-format, PDF output.

Style guide for writing behavioral eval criteria. Use when creating, reviewing, or modifying evals in .crews/evals.yaml to ensure reliable LLM-based grading.

Git commit and push workflow. Use when committing changes, pushing to remote, or managing branches.

Kiro CLI agent JSON schema, valid fields, tool mappings, hooks, and common mistakes. Use when creating or modifying crew YAML or agent configurations.

Create effective presentations, slide decks, and workshop materials. Use when building MARP decks, PowerPoint content, demo scripts, or any audience-facing material.

Write and improve README files that orient readers and drive adoption. Use when creating, rewriting, or auditing a project README. Trigger terms: readme, README, project description, quick start, getting started, project documentation entry point.

Patterns for reviewing kiro-cli session transcripts. Use when analyzing sessions for protocol compliance, performance issues, or crew improvements.

Systematic debugging methodology. Use when encountering errors, investigating failures, or diagnosing issues.

Author hands-on tutorials that take readers from zero to a working result. Use when producing a new tutorial, getting-started guide, onboarding doc, or restructuring docs that drifted from tutorial into reference. Trigger terms: tutorial, getting started, onboarding, step-by-step guide, walkthrough, hands-on, learning guide.

Gate workflow for verifying work before reporting DONE. Use when completing a task, marking work finished, or about to signal DONE.

Writing style for technical documentation, README files, guides, and any user-facing text. Use when writing or reviewing prose, docs, comments, commit messages, or PR descriptions. Trigger terms: writing, prose, documentation style, tone, clarity, technical writing.

Create or restructure skills for agent crews. Use when creating a new skill, splitting a skill that's too large, or converting a single-file skill to multi-file.