# 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).

- Skill: `ryan-scheinberg/role-stint-plan` (Agent Skill)
- Install (CLI): `npx skillmds@latest add ryan-scheinberg/role-stint-plan`
- Raw SKILL.md: https://api.skillmd.com/api/skills/ryan-scheinberg/role-stint-plan/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: ryan-scheinberg (https://skillmd.com/u/ryan-scheinberg)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/ryan-scheinberg/role-stint-plan

---


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.