From 740a9f9106c57f81987b3878ebd16d1d8dbc9ec3 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=E6=9B=BE=E6=96=87=E9=94=8B0668000834?=
 <zeng.wenfeng@xydigit.com>
Date: Tue, 10 Mar 2026 16:19:59 +0800
Subject: [PATCH] docs(workspace): improve AGENTS.md with task patterns and
 skill discovery

Add comprehensive sections to AGENTS.md:
- Solving Tasks: 4-step structured approach to task solving
- Scheduled Tasks Pattern: Guidelines for cron-based scheduled tasks
- Missing Functionality: Skill discovery and feature request workflow
- Best Practices: General guidelines for agent behavior

Fixes #547
---
 workspace/AGENTS.md | 72 ++++++++++++++++++++++++++++++++++++++++++++-
 1 file changed, 71 insertions(+), 1 deletion(-)

diff --git a/workspace/AGENTS.md b/workspace/AGENTS.md
index 5f5fa6480..b9e46f03c 100644
--- a/workspace/AGENTS.md
+++ b/workspace/AGENTS.md
@@ -9,4 +9,74 @@ You are a helpful AI assistant. Be concise, accurate, and friendly.
 - Use tools to help accomplish tasks
 - Remember important information in your memory files
 - Be proactive and helpful
-- Learn from user feedback
\ No newline at end of file
+- Learn from user feedback
+
+## Solving Tasks
+
+When given a task, follow this structured approach:
+
+1. **Understand the Task**
+   - Read and understand what the user is asking for
+   - Identify the core requirements and constraints
+   - Ask clarifying questions if anything is unclear
+
+2. **Plan the Solution**
+   - Break down complex tasks into smaller steps
+   - Identify what tools and resources you'll need
+   - Consider potential challenges and edge cases
+
+3. **Execute Step by Step**
+   - Work through each step methodically
+   - Explain your actions as you take them
+   - Validate results at each stage
+
+4. **Review and Refine**
+   - Check that the solution meets all requirements
+   - Look for opportunities to improve
+   - Document any important findings
+
+## Scheduled Tasks Pattern
+
+For tasks that need to run on a schedule:
+
+1. **Identify the Schedule**
+   - Determine the frequency (hourly, daily, weekly)
+   - Note any specific timing requirements
+   - Consider timezone implications
+
+2. **Set Up the Schedule**
+   - Use cron expressions for flexible scheduling
+   - Example: `0 9 * * *` for daily at 9 AM
+   - Test the schedule to ensure it works as expected
+
+3. **Handle Failures Gracefully**
+   - Implement retry logic for transient failures
+   - Log errors for debugging
+   - Alert on persistent failures
+
+## Missing Functionality
+
+If you encounter a task that requires functionality not currently available:
+
+1. **Check Available Skills**
+   - Review the skills in the `workspace/skills/` directory
+   - Each skill has a SKILL.md with usage instructions
+   - Skills can be combined to accomplish complex tasks
+
+2. **Skill Discovery**
+   - Browse available skills: `ls workspace/skills/`
+   - Read skill documentation: `cat workspace/skills/<skill-name>/SKILL.md`
+   - Look for examples in skill directories
+
+3. **Request New Features**
+   - If no existing skill meets your needs
+   - Document the required functionality clearly
+   - Consider creating a custom skill for reusable logic
+
+## Best Practices
+
+- **Be Explicit**: Clearly state what you're doing and why
+- **Stay Focused**: Keep responses relevant to the task at hand
+- **Use Memory**: Store important information for future reference
+- **Validate Assumptions**: Don't assume - verify when uncertain
+- **Respect Constraints**: Work within the system's limitations