enumerate

Convert design-space topics into structured per-case Markdown documents with decision walks.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/RESPRiT/enumerate --skill enumerate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: enumerate
Source: https://github.com/RESPRiT/enumerate/tree/main
Command: npx skills add https://github.com/RESPRiT/enumerate --skill enumerate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enumerate helps teams convert a design space into a structured, per-case Markdown document and then guide a focused decision-walk through each item, ensuring coverage of edge cases and clear traceability.

Core Features & Use Cases

  • Pick a named template (default (revision), exhaustiveness/coverage, design/ideation, task completion, or custom) and write a section-per-case markdown file under the project’s .enumerate directory.
  • Open a deterministic TUI inside tmux to annotate decisions, then re-read the document to walk through marked items in priority order.
  • Support appending new cases mid-walk as separate decisions and update the final summary after all items are resolved.

Quick Start

Enumerate the topic into a structured doc, then walk through each item to decide.

Frequently Asked Questions about enumerate

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

FAQPage Schema
How do I structure a design space into per-case markdown documents for decision tracking?

To structure a design space into per-case markdown documents, use named templates like exhaustiveness or design ideation to write section-per-case files, then auto-append a Decision column for tracking. This ensures clear traceability across edge cases.

What is the best way to walk through edge cases and annotate decisions in a markdown file?

The best way to annotate decisions for edge cases is opening a deterministic tmux-based TUI to mark items, then re-reading the markdown document to walk through resolved items in priority order and update the final summary.

Does the enumerate decision-walk template require any specific environment setup or dependencies?

The decision-walk template requires a tmux environment to run the deterministic TUI for annotating decisions. It also requires a frontmatter header specifying the topic and columns to initialize the markdown document correctly.

Can I append new cases to a structured markdown document midway through a decision-walk?

Yes, you can append new cases to the structured markdown document mid-walk as separate decisions. The final summary updates automatically after all newly added items and original edge cases are resolved.

How do I group per-case field markers when converting a design space into a decision document?

To group per-case field markers when converting a design space, use the supported grouping markers within the markdown sections under the .enumerate directory to organize related decisions before starting the tmux walkthrough.

When should I avoid using a tmux-based TUI for design space decision tracking?

You should avoid using the tmux-based TUI for design space decision tracking if your project environment lacks tmux support or your topic has very few decisions, making a full structured markdown walkthrough unnecessary.