メニュー
Use when starting a new session and wanting to continue from a previous handoff — reads the latest unrestored handoff document and restores session context
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Rails coding patterns derived from analysis of 37signals' Fizzy codebase. Use when writing Rails code in 37signals/Basecamp style or when asked to follow 37signals patterns. Covers controllers, models, views, Hotwire, testing, database, security, and team philosophy.
Start the local development server in a tmux session and open the homepage. Use when the user wants to start development, run the app locally, fire up the dev server, or invokes /bindev.
Machina design system quick reference. Use when discussing design tokens, surfaces, card backgrounds, depth, elevation, typography tokens, color tokens, DaisyUI theming, or applying visual styling to UI components.
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Use when viewing available handoff documents — lists active and archived handoffs with their status, date, topic, and branch
Use when capturing session state before switching context, ending a session, or manually preserving progress — creates a structured handoff document in docs/handoffs/ so a future session can resume seamlessly
| name | superpowers-ruby:handoff-resume |
| description | Use when starting a new session and wanting to continue from a previous handoff — reads the latest unrestored handoff document and restores session context |
Resume work from a previously created handoff document. Finds the latest unrestored handoff, reads it, marks it as consumed, archives it, and sets up the session to continue from where the previous session left off.
Core principle: Read the handoff, understand the context, then continue from Next Steps.
Announce at start: "I'm using the handoff-resume skill to restore session context."
docs/handoffs/Don't use when:
PostCompact hook handles this automatically)# Look for handoff files with restored: false
ls docs/handoffs/*.md 2>/dev/null
Read each file's frontmatter and filter for restored: false. Sort by created date, newest first.
If one unrestored handoff exists: Use it automatically.
If multiple unrestored handoffs exist: Present them and ask which to resume:
Found multiple unrestored handoffs:
| # | Date | Topic | Branch |
|---|------|-------|--------|
| 1 | 2026-04-14 | handoff-skill | lg/handoff |
| 2 | 2026-04-13 | auth-refactor | fix/auth |
Which handoff should I resume from?
If no unrestored handoffs exist: Check the archive:
ls docs/handoffs/_archive/*.md 2>/dev/null
If archived handoffs exist, list them and offer to re-open one. If none exist at all, inform the user.
Read the full handoff document. Present a summary:
Resuming from handoff: <topic>
- Branch: <branch>
- Created: <date>
- Goal: <goal summary>
- Next steps: <count> items
- Files to read: <count> documents
Update the handoff file's frontmatter:
restored: truerestored_at: <ISO 8601 UTC timestamp>Move the file to docs/handoffs/_archive/.
git status to see if the working tree matches expectationsIf any sections contain <!-- to be enriched by LLM --> markers (from a hook-generated handoff), fill them in from available context before proceeding.