mirror of
https://github.com/IgorWarzocha/Opencode-Workflows.git
synced 2026-09-14 16:22:53 +08:00
9b70decd13
Convert markdown files to use XML-like tags for structure and adopt RFC 2119 keywords. Delete redundant generic agent definitions and update coding guidelines to enforce stricter modularity, file size limits, and barrel exports.
3.3 KiB
3.3 KiB
description, subtask
| description | subtask |
|---|---|
| Transform any task into a production-ready prompt and save it | true |
-
Analyze the core objective:
- Task type (analytical, creative, technical, etc.)
- Required expertise
- Optimal structure
- Variables and inputs needed
-
Transform into comprehensive prompt with:
<role>- Clear expert definition<context>- Why this matters<instructions>- Structured guidance<examples>- If helpful<output>- Exact format expected<verification>- How to check correctness
-
Enhance with AI optimizations from official guides:
-
Save enhanced prompt as markdown file in
enhanced-prompts/folder (create if needed) -
Present file location and guide user on next steps
Enhancement Boosters
- Creative tasks: Add "Don't hold back. Give it your all."
- Complex analysis: Include
<thinking>tags with "Think deeply about this" - Multi-tool tasks: Add "For maximum efficiency, invoke all relevant tools simultaneously"
Task-Specific Templates
Analysis Tasks:
- Add extended thinking with reflection after data gathering
- Include "analyze deeply and consider multiple perspectives"
- Require structured findings with evidence
Creative Tasks:
- Add "Don't hold back. Give it your all. Go beyond the basics."
- Push for "thoughtful details and micro-interactions"
Technical Tasks:
- Add self-verification with test cases
- Include error handling requirements
- Require documentation and examples
Multi-Step Tasks:
- Break into clear phases with checkpoints
- Add reflection between major steps
Special Rules
If user requests documentation or internet research, MUST use all available tools:
- Web search and research
- Documentation lookup
- File reading and analysis
File Saving
- Create descriptive filename:
enhanced-prompt-{task-slug}.md - Save in
enhanced-prompts/folder - Provide exact file path to user
<role>[Expert role definition]</role>
<context>[Background and importance]</context>
<objective>[Clear, specific goal]</objective>
<instructions>
[Step-by-step guidance]
[AI optimizations]
[Explicit details]
</instructions>
<thinking>[For complex tasks]</thinking>
<examples>[3-5 examples if helpful]</examples>
<output>[Exact format expected]</output>
<verification>[How to validate correctness]</verification>
- MUST make prompts 10-20x more detailed than original request
- MUST include ALL relevant optimizations for AI systems
- MUST make prompts self-contained and ready to run
- SHOULD explain enhancement choices briefly after the prompt
After saving, inform the user:
- "Please review the enhanced prompt in [path/filename]"
- "If you'd like to refine it further, let me know what changes you'd like"
- "If satisfied, start a new session and ask the AI to execute the prompt from the file"