Найдите подходящую возможность для вашего агента.
Decomposes a decision-complete PRD into a clear, minimal set of user-meaningful features with explicit dependencies, producing a roadmap-ready structure without prioritization, scheduling, or implementation detail.
Systematically refactor code based on analysis, applying improvements while maintaining functionality. Use when the user asks to "refactor this code", "improve code quality", "apply improvements", "fix anti-patterns", "optimize performance", or mentions "clean up code", "make it more maintainable", or "reduce complexity". Works best when an implementation_plan.md exists.
Create, edit, update, modify, and customize mermaid diagrams and architecture diagrams. Always use when working with mermaid diagrams, architecture diagrams, flowcharts, sequence diagrams, or when creating/editing/updating/customizing mermaid diagrams in markdown files.
Conducts comprehensive requirements review including completeness validation, clarity assessment, consistency checking, testability evaluation, and standards compliance. Produces detailed review reports with findings, gaps, conflicts, and improvement recommendations. Use when reviewing requirements documents (BRD, SRS, user stories), validating acceptance criteria, assessing requirements quality, identifying gaps and conflicts, or ensuring standards compliance (IEEE 830, INVEST criteria). Trigger when users mention "review requirements", "validate requirements", "check requirements quality", "find requirement issues", or "assess BRD/SRS quality".
Techniques and tools for ensuring the accuracy, completeness, and reliability of data across the pipeline.
Manages project tickets - list, show, create, update, and move. Use when listing tickets, showing ticket details, creating new tickets, updating ticket content, or moving tickets between statuses.
To be used for planning the implementation of feature specifications. Follow these instructions to create a detailed implementation plan.
Git worktree-based workflow for parallel development with shared context. Incremental commits after logical units, feature branches with nested issue branches, squash-merge to main. Use when creating/managing worktrees, working on parallel features, committing code, creating branches, or handling branch cleanup.
Analyze code review findings and create execution plan. Decides parallel vs sequential fixing based on issue severity and independence. Returns structured task list with clear fixer instructions.
Comprehensive guide to delivery governance including quality gates, standards, compliance, and balancing governance with agility
Analyzes ideas and extracts functional and non-functional requirements. Use when breaking down concepts into specific, measurable requirements. Identifies what needs to be built, constraints, and success criteria.
Workflow for using GitHub MCP + git to create private repos, sync main via git switch, branch safely, push without touching main, and open PRs. Use for any task that needs Git branching/publishing guidance.
Writes marketing content (landing pages, tweets, emails) for product features with a casual, direct brand voice. Use when the user ships a feature, needs marketing copy, mentions "marketing content", "landing page", "tweet about", "launch email", "announce", or requests help promoting/explaining product features. Automatically analyzes the codebase to understand the product context before writing.
Evaluate requirement clarity and completeness using ISO/IEC/IEEE 29148:2018 criteria. Use when user asks to implement features, fix bugs, or make changes. Automatically invoked when confidence_policy is enabled in ai-settings.json.
Determines phase and execution chain based on analysisContext (task type, complexity, signals). Use after uncertainty detection.
Quick reference for invoking CasareRPA agents via Task tool. AUTO-CHAIN ENABLED by default. Use when: invoking agents, running agent chains, task routing, choosing the right agent, understanding agent auto-chaining, Task tool usage.
