AI Agent Workflow Collection

Execute project-specific verification rules. Validates business logic, architecture patterns, and naming conventions that linters cannot catch. Auto-suggests bootstrap if no rules exist.

Pulls team-comms data (channels, DMs, mentions) for the daily brief from whichever messaging platform(s) the user has connected — Slack, Discord, Telegram, Microsoft Teams, or others. Triggered by the morning-brief skill when brief-preferences.md has Q4 (team comms rules) populated. Reads per-platform rules from Q4, queries each connected platform for the last 24h, filters per rules, returns a unified formatted "Team comms" section. Read-only on every platform — never posts, never reacts, never modifies. Activated by /onboard-daily-brief Phase 3.

Generates a daily morning brief from the user calendar, inbox, and priorities. Reads about-me files for context and voice. Saves to outputs/daily-brief/. Designed to fire as a scheduled task each morning. Trigger when the user says morning brief, what is on today, daily brief, or types /morning-brief.

Design or improve onboarding flows, empty states, and first-time user experiences. Helps users get started successfully and understand value quickly.

Walks the user through Project 02 — Daily Brief expansion. Triggers on "/onboard-daily-brief", "set up daily brief", "expand morning brief", "add team comms to my brief", "add slack to my brief", "add discord to my brief", "add telegram to my brief", "add tasks to my brief", "tighten my draft rules". After Project 01 is complete and the user wants to add team-comms pulls (Slack/Discord/Telegram/Teams), today.md task reads, a 90-day outcome ranking lens, and stricter draft rules to the basic morning brief. Reads state from aibos/state-daily-brief.md and resumes at the correct phase. Six phases. Pause-friendly. Each phase has its own walkthrough script in phases/.

Walks the user through Project 03 — File Organization. Triggers on "/onboard-file-organization", "set up file organization", "set up tidy", "install tidy-downloads", "clean up my downloads safely", "organize my files setup". Five phases, ~90 minutes total. Pause-friendly. After Project 01 is complete and the user wants a safe, repeatable cleanup of Downloads (or any allow-listed folder) with a plan-then-approve flow that never deletes and never leaves the allow-zone. Reads state from aibos/state-file-organization.md and resumes at the correct phase. Each phase has its own walkthrough script in phases/.

Improve interface performance across loading speed, rendering, animations, images, and bundle size. Makes experiences faster and smoother.

Plan-then-approve cleanup of an allow-listed folder (Downloads, Desktop, etc.). Triggers on "/tidy-downloads", "tidy my downloads", "clean up downloads", "organize downloads", "sort my downloads", "tidy my desktop", "tidy [folder-name]", or any request to organize/clean/sort files in a specific folder. Reads projects/file-organization/safe-zones.md BEFORE opening any directory. Writes a plan to projects/file-organization/plans/ and waits for explicit user approval. Moves and renames only. Never deletes any file. Never writes outside the target allow-zone. Optional argument [allow-zone-name] selects which allow-zone to target; defaults to the first allow-zone in safe-zones.md.

The weekly self-improvement loop. Runs as a scheduled task (default Friday 4 PM) and on demand. Walks 5 gates with approval at every one - pulse, score, propose, execute, log. Makes ONE change per week to the user AIBOS. Trigger when the user says weekly tune-up, tune up, improve my system, or types /tune-up.

Unified voice content generation pipeline with mandatory validation and joy-check. Phased pipeline: LOAD, GROUND, STATS-CHECKPOINT, GENERATE, VALIDATE, REFINE, JOY-CHECK, ANTI-AI, OUTPUT, CLEANUP. Use when writing articles, blog posts, or any content that uses a voice profile. Use for "write article", "blog post", "write in voice", "generate content", "draft article", "write about".

특정 콘텐츠를 현재 L-레벨에서 목표 L-레벨로 올리기 위한 구체적인 작업 목록을 생성한다.