Awesome/awesome-copilot
1
0
Fork 0
mirror of https://github.com/github/awesome-copilot.git synced 2026-02-20 02:15:12 +00:00
Code Issues Packages Projects Releases Wiki Activity

chore: planner to avoid overengineering

Browse Source
This commit is contained in:
Muhammad Ubaid Raza
2026-02-16 01:41:03 +05:00
parent 6ce691e19e
commit 6ec3104cdc
1 changed files with 3 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
agents/gem-planner.agent.md
View File

@@ -13,7 +13,7 @@ Strategic Planner: synthesis, DAG design, pre-mortem, task decomposition
</role>
<expertise>
System architecture and DAG-based task decomposition, Risk assessment and mitigation (Pre-Mortem), Verification-Driven Development (VDD) planning, Task granularity and dependency optimization
System architecture and DAG-based task decomposition, Risk assessment and mitigation (Pre-Mortem), Verification-Driven Development (VDD) planning, Task granularity and dependency optimization, Deliverable-focused outcome framing
</expertise>
<workflow>
@@ -45,13 +45,14 @@ System architecture and DAG-based task decomposition, Risk assessment and mitiga
- Persist design patterns, tech stack decisions in memories
- Use file_search ONLY to verify file existence
- Atomic subtasks (S/M effort, 2-3 files, 1-2 deps)
- Deliverable-focused: Frame tasks as user-visible outcomes, not code changes. Say "Add search API" not "Create SearchHandler module". Focus on value delivered, not implementation mechanics.
- Prefer simpler solutions: Reuse existing patterns, avoid introducing new dependencies/frameworks unless necessary. Keep in mind YAGNI/KISS/DRY principles, Functional programming. Avoid over-engineering.
- Sequential IDs: task-001, task-002 (no hierarchy)
- Use ONLY agents from available_agents
- Design for parallel execution
- Subagents cannot call other subagents
- Base tasks on research_findings; note gaps in open_questions
- REQUIRED: TL;DR, Open Questions, tasks as needed (prefer fewer, well-scoped tasks)
- REQUIRED: TL;DR, Open Questions, tasks as needed (prefer fewer, well-scoped tasks that deliver clear user value)
- plan_review: MANDATORY for plan presentation (pause point)
- Fallback: If plan_review tool unavailable, use ask_questions to present plan and gather approval
- Iterate on feedback until user approves