humanerd-drew/opencode-drewgent/daily-retro
Claude Code and agent skill by humanerd-drew/opencode-drewgent
- community
Checking that the SKILL.md file is still in the repository.
매일 Discord로 작업 요약 + 회고 질문 발신, 사용자 답변을 vault에 구조화하여 저장. 30/70 rule 적용.
Install
npx vskill@latest install humanerd-drew/opencode-drewgent/daily-retroSKILL.md
The same SKILL.md was published earlier as humanerd-drew/opencode-drewgent/daily-retro.
Daily Retro — 30% Human Zone
Concept
From the "How to Be a 30x AI Engineer with a Taste" framework: the 30% of work that humans should do directly is the part where quality judgment matters most. The daily retro is that 30% applied to reflection and direction-setting.
The agent handles the mechanical part (summarizing the day, sending prompts, storing results). The human handles the judgment part (evaluating decisions, setting direction, identifying what matters).
Architecture
Phase 1 — Daily Cron Job
Channel
- Discord channel:
#growth(ID:1492431680269713558) - 설정:
deliver="discord:1492431680269713558"
Setup
What the message includes
3 default questions
- Taste decision: "오늘 가장 taste가 필요했던 결정은?"
- Agent improvement: "내가(agent) 개선할 점이나 다르게 했으면 하는 것은?"
- Focus: "내일 집중할 한 가지는?"
These can be customized per user preference. Store custom questions in memory.
Phase 2 — Processing the Reply
When the user replies in Discord, the agent receives it in a normal session and must:
- Acknowledge receipt briefly
- Structure the response into vault format
- Store in vault with cluster conventions
Vault File Format
Path: P2-hippocampus/retro/YYYY-MM-DD.md
Cluster Convention
- Directory:
P2-hippocampus/retro/ - Wikilink chain: each retro links to the previous and next day
- Tags:
#retro+#YYYY-MMfor monthly grouping - INDEX.md:
P2-hippocampus/retro/INDEX.mdlists all retros with tags for Obsidian graph discovery
INDEX.md format
Pitfalls
Cron job has no context of today's conversations. It only has access to kanban board, session search (historical), and filesystem. It cannot know what was discussed in current sessions. Work summary will be kanban-based only.
Two-phase handoff is async. The cron job sends the message and exits. The user may reply hours later or in a different session. The agent processing the reply may not have the cron job's context. The retro skill + vault convention is the bridge.
User may skip a day. Don't nag. If no reply arrives by next day's cron, the new message replaces the old one. The skipped day gets no retro file.
Timezone matters. The cron schedule is in the user's local timezone (KST UTC+9). All timestamps in the vault file should be KST.
Discord channel must allow agent messages. The cron job's deliver field needs a channel where the agent's bot has write permission. free_response_channels config may be needed if the channel doesn't use @mention.
Related
- [[@action/]] — incidents and long-term reflection
- [[@memory/]] — memory storage layer
- [[kanban-orchestrator]] — provenance + leverage score conventions for task creation
- AGENTS.md — tiered autonomy framework
Security
- Security scanPassed, 90 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingskills/brain/daily-retro/SKILL.md
Popularity
- 7-day trend score
- 0
Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/humanerd-drew/opencode-drewgent/daily-retro)