원클릭으로
accomplish
// Log an accomplishment to Daily_Accomplishments and session-context. Use when the user wants to record a win, milestone, or personal achievement.
// Log an accomplishment to Daily_Accomplishments and session-context. Use when the user wants to record a win, milestone, or personal achievement.
Refactor any skill by extracting deterministic operations into a Python script and slimming the SKILL.md to only AI judgment parts. Use when user says /codify, codify a skill, or optimize a skill.
Smart PRD generator with TaskMaster integration. Detects existing PRDs and offers execute/update/replace options. Generates comprehensive technical PRDs optimized for task breakdown, validates with 13 automated checks, and optionally executes tasks autonomously with datetime tracking and rollback support. Use when user requests "PRD", "product requirements", or mentions task-driven development. Defaults to PRD generation with handoff to TaskMaster. Optionally supports autonomous execution with 4 modes.
Use when writing ANY implementation code, fixing bugs, or modifying existing code. Delegates research to a fast subagent that distills WebSearch results into compact RAG-efficient summaries. Main context never sees raw output.
Session initialization and lifecycle management: bootstraps session context, organizes files, generates CLAUDE.md, manages soul purpose lifecycle with completion protocol and active context harvesting. Use when user says /start, /init, bootstrap session, initialize session, or organize project.
| name | accomplish |
| description | Log an accomplishment to Daily_Accomplishments and session-context. Use when the user wants to record a win, milestone, or personal achievement. |
| triggers | ["/accomplish","log accomplishment","record accomplishment","add accomplishment"] |
| user-invocable | true |
| allowed-tools | ["Bash","Edit","Write","Read","AskUserQuestion"] |
Script: ~/.claude/skills/accomplish/script.py handles all file I/O.
/accomplish <description of what was accomplished>
If user provided a description, use it as ACCOMPLISHMENT_TEXT. Otherwise ask:
question: "What did you accomplish?"
header: "Win"
options: []
multiSelect: false
python3 ~/.claude/skills/accomplish/script.py gather-context
Returns JSON with: date_file, timestamp, daily_path, daily_exists, session_context_path, has_accomplishments_section, git_log, git_diff.
Using ACCOMPLISHMENT_TEXT, git_log, git_diff, and session context, craft:
### TIMESTAMP AEDT
**What**: Brief title (from ACCOMPLISHMENT_TEXT)
**Context**: Why this matters — connect to user's journey, business goals, or growth
**Details**: Specifics — repos, files, tools, metrics
**Reflection**: Mirror the user's sentiment genuinely
Keep tone authentic. If they're excited, let it show. If it was hard-won, note the struggle. Include tables if the accomplishment involves structured data.
python3 ~/.claude/skills/accomplish/script.py write-entry \
--file "DAILY_PATH" \
--entry "FORMATTED_ENTRY" \
--create # only if daily_exists is false
Only if session_context_path was found:
python3 ~/.claude/skills/accomplish/script.py write-mirror \
--file "SESSION_CONTEXT_PATH" \
--line "**TIMESTAMP AEDT** - One-liner summary"
Output briefly:
Logged to ~/Hermes/Daily_Accomplishments/DATE_FILE.md
Mirrored to session-context/CLAUDE-activeContext.md
~/Hermes/Daily_Accomplishments/ (FIXED)session-context/ lives relative to cwd)All commands output JSON. Run from any directory.
| Command | Purpose |
|---|---|
gather-context | Get date/time (AEDT), git log/diff, file paths and existence flags |
write-entry --file PATH --entry TEXT [--create] | Write/append formatted entry to daily file |
write-mirror --file PATH --line TEXT | Append one-liner to Accomplishments section in session-context |