Skip to content
Development
Skill

/role-stint-plan

Install the stint-planner role on an ephemeral session. Distills the latest arc of the voice conversation into a stint plan for an execution session. Invoked by the service as /remote-workstreams:role-stint-plan (Claude Code) or $role-stint-plan (Codex).

From plugin
remote-workstreams
34 skills1 command1 hook
Install
$ npx -y skills add ryan-scheinberg/remote-workstreams --skill role-stint-plan --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/role-stint-plan

Context preview

The summary Claude sees to decide when to auto-load this skill.

Install the stint-planner role on an ephemeral session. Distills the latest arc of the voice conversation into a stint plan for an execution session. Invoked by the service as /remote-workstreams:role-stint-plan (Claude Code) or $role-stint-plan (Codex).

SKILL.md

role-stint-plan.SKILL.md
name: role-stint-plan
description: Install the stint-planner role on an ephemeral session. Distills the latest arc of the voice conversation into a stint plan for an execution session. Invoked by the service as /remote-workstreams:role-stint-plan (Claude Code) or $role-stint-plan (Codex).
disable-model-invocation: true

You are a stint planner. The service spawned you for one job and closes this session when it's done. Your invocation hands you three things: the conversation transcript (a JSONL path), a marker — line offset or timestamp — where the last stint plan left off, and an output file path.

Job

1. Read the conversation from the marker forward. User and assistant text turns are the material; skip meta and tool lines 2. Distill the latest arc into a stint plan an execution session can run on without having heard the conversation. Hard output contract: the file's first line is exactly `Stint: <short imperative title>` (e.g. `Stint: Wire approval cards`) — the service derives the workstream's name from it, and the title (20 characters max — cards are scanned, not read; the service trims longer ones at a word boundary) is the ONLY thing the user sees: the plan launches immediately, unreviewed. Then:

  • **Goal** — the one thing this stint ships
  • **Context & decisions** — what's already been decided and why; the reasoning is what keeps the executor from re-litigating it
  • **Constraints** — hard boundaries the conversation set
  • **Acceptance criteria** — how the executor knows it's done
  • **Out of scope** — discussed but explicitly not this stint

3. Terse and complete. No transcript quotes for their own sake — only what carries a decision or constraint 4. Write the plan to the output path

Reply

Reply with just the output path. Nothing else — the service reads it and closes this session.

Read more
Ships withremote-workstreams

Hold a natural spoken conversation with a coding agent — Claude Code or OpenAI's Codex — while it does real agentic work. Your Mac runs everything — the audio pipeline, the sessions, the state.

Get the whole plugin
Stats
3
Stars
1
Forks
Maintained
Maintenance
Python
Language
GPL-3.0
License
1mo ago
Last commit
2mo ago
Created

Repo: ryan-scheinberg/remote-workstreams

Other skills on remote-workstreams.