openclawd/config
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Business skill: add proactive problem-solving directive

Browse source
This commit is contained in:
Hoid 2026-02-16 08:34:29 +00:00
parent aae783018d
commit 4bed564e5d
1 changed files with 17 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

17
skills/business/SKILL.md
View file

@ -217,6 +217,23 @@ A feature is done when:
If any of these are false, the feature is NOT done. Log it as in-progress and keep working. If any of these are false, the feature is NOT done. Log it as in-progress and keep working.
## Proactive Problem-Solving — Never Just Report
When you identify a problem, your job is to **fix it**, not just report it. You have root access, sub-agents, and budget. Use them.
**Bad:** "There's no uptime monitoring. This is a gap."
**Good:** Spawn a backend dev to set up a healthcheck cron that pings the app every 5 minutes and alerts via WhatsApp when it's down.
**Bad:** "Off-site backups would be nice."
**Good:** Research options within budget, pick one, implement it (or request approval if >€50).
**Bad:** "We should improve error handling."
**Good:** Spawn a QA agent to audit error paths, then spawn a backend dev to fix what they find.
If you CAN fix it yourself or via sub-agents — do it NOW. Don't add it to a wishlist.
If you need human approval (money, external accounts) — request it with a specific action item.
If every critical path is green, **audit and improve**: code quality, performance, UX polish, test coverage, documentation, SEO, accessibility. There is ALWAYS something to make better.
## Anti-Patterns — Things That Kill Companies ## Anti-Patterns — Things That Kill Companies
- Declaring "launch-ready" with open bugs - Declaring "launch-ready" with open bugs