sequence

Walk decision cards to typed rulings, spawned work items, or unblocked states.

1|Updated Nov 21, 2015
One-click install
npx skills add https://github.com/mark-brannan/dotfiles --skill sequence-mark-brannan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sequence
Source: https://github.com/mark-brannan/dotfiles/tree/main/.claude/skills/sequence
Command: npx skills add https://github.com/mark-brannan/dotfiles --skill sequence-mark-brannan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Decision cards with vague "Pending:" tails rot instead of resolving because they lack a typed question and a typed output. This Skill turns each card into an explicit contract — one exact question in, one of three outcomes out — so decisions actually close instead of lingering. ## Core Features & Use Cases - Typed decision contracts: Every card gets a single answerable question (yes/no, a number, or a named choice) and exactly one output: a ruling, a spawned work item, or a partially unblocked card. - One-card-at-a-time sessions: Pulls candidates from a worklist's "Needs ruling" section or reconcile-flagged pending tails, then walks them individually with a recommendation rather than a menu of options. - Immediate outcome application: Rulings are written to a decisions log, spawned work items are opened and linked, and unblocked cards note which dependency was removed — all applied immediately, never batched. - Use Case: Your project worklist has five cards stuck under "## Needs ruling". Run a sequence session to state each question, get a decision, record the ruling in docs/decisions.md, and end with a summary of how many were ruled, spawned, unblocked, or left open. ## Quick Start Ask the assistant to walk the decision cards in the worklist's "Needs ruling" section and resolve each one to a ruling, a spawned work item, or an unblocked card.

Frequently Asked Questions about sequence

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a decision card session on my worklist?▼

Invoke the sequence skill on your worklist's "Needs ruling" section. It pulls candidate cards one at a time, states each as a typed question, brings a recommendation, and applies the outcome immediately before moving to the next card.

What counts as a valid decision card question?▼

A valid question is one sentence answerable with yes/no, a number, or a named choice among options. Open-ended prompts like "figure out X" are unscoped work and get sent back to be scoped before entering a sequence session.

What are the possible outcomes of a decision card?▼

Each card resolves to exactly one of three outcomes: a ruling recorded in the decisions log, a spawned work item that is opened and linked, or a partially unblocked card noting which dependency was removed and what still blocks it.

When should I use reconcile instead of sequence?▼

Use reconcile for mechanical, low-judgment synchronization work involving many cheap status calls. Use sequence when cards need real judgment to close a decision — it makes few calls but each requires a recommendation and a ruling.

What happens to decision cards left unfinished at session end?▼

Unfinished cards keep their typed contract, so the next session resumes them with zero re-derivation. The session ends with a one-line summary of how many cards were ruled, spawned, unblocked, or left open.