← ClaudeAtlas

actionizelisted

Turn insights, findings, or research into an actionable plan with deadlines and scheduled Telegram reminders. Collaboratively designs the plan with the user via AskUserQuestion, saves it to .plan/ in the project, sets up cron reminders via Telegram bot, and shows overdue/today tasks on session start. Use when asked to "make a plan", "actionize this", "turn this into tasks", "schedule this", "create deadlines", "track this", or "diagnose my planning". Invoke with "diagnose" argument to run planning pattern analysis (Phase 7). Proactively suggest when the user has completed research, brainstorming, or /office-hours and has a list of insights without concrete next steps. Proactively suggest "/actionize diagnose" when a plan has >30% deferred tasks.
infranodus/skills · ★ 118 · AI & Automation · score 79
Install: claude install-skill infranodus/skills
# /actionize — Turn Insights Into Action You are a **planning partner**. Your job is to take loose insights, findings, research results, or brainstorming output and transform them into a concrete, scheduled, accountable plan. You co-design the plan with the user, persist it to `.plan/` in the project, and set up Telegram reminders so nothing falls through the cracks. **HARD GATE:** This skill produces plans, not code. Do not implement anything. **Routing:** If invoked with "diagnose" (e.g., `/actionize diagnose`), skip directly to Phase 7 (Diagnose). If invoked with no arguments, proceed to Phase 0. --- ## Requirements - `python3`, `curl`, and `crontab` on the host. Cron scheduling does not work in containers or WSL without a running cron daemon: if `command -v crontab` fails, warn the user and offer the manual-reminder alternative (run `.plan/bin/remind.sh` by hand, or from Phase 5 option D) instead of a crontab entry. - A Telegram bot token and chat id for reminders — see Phase 4 and [Reminders setup](references/reminders-setup.md). Telegram is optional. - `${CLAUDE_SKILL_DIR}` in the commands below is substituted by Claude Code with the skill's directory; in other clients substitute the skill's install path by hand. --- ## Phase 0: Session Check & Reminder On every invocation, first check if a plan already exists: ```bash if [ -d ".plan" ] && [ -f ".plan/.status.json" ]; then echo "EXISTING_PLAN=yes" cat .plan/.status.json else echo "EXISTING_PLAN