skills.rest
Ratler
RatlerCOMMUNITY
Explore all skills by this author →
GitHub

spec-sequential

Convert brainstorming conversations into formal sequential execution specs.

16|3|Updated Feb 7, 2026
Search Tags:#automation#planning#spec#task-management#builder#sequential
One-click install
npx skills add https://github.com/Ratler/dream-team --skill spec-sequential
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-sequential
Source: https://github.com/Ratler/dream-team/tree/main/skills/spec-sequential
Command: npx skills add https://github.com/Ratler/dream-team --skill spec-sequential

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Convert a brainstorming session into a formal, linear execution spec for sequential tasks.

Core Features & Use Cases

  • Write a formal, sequential spec from conversational planning; ensures tasks run strictly in order with no parallel sub-agents.
  • Auto-injects required frontmatter fields (mode, spec-version, playwright, frontend-design) and provides a structured task list to guide implementation and validation.
  • Use Case: After a brainstorming session, generate specs to drive a single-threaded build workflow and reduce ambiguity.

Quick Start

Summarize the agreed plan from the conversation and write the sequential spec according to the guide.

Frequently Asked Questions about spec-sequential

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

FAQPage Schema
How do I convert brainstorming sessions into a sequential execution spec?▼

To convert brainstorming sessions into a sequential execution spec, summarize the agreed plan from your conversation and generate a formal task list. This enforces strict linear execution with no parallel agents across tasks.

What is a linear spec for single-session task management?▼

A linear spec for single-session task management is a formal execution plan that defines a strict sequential order for tasks. It ensures single-threaded build workflows by preventing parallel sub-agents and reducing ambiguity.

What frontmatter fields are required for a sequential execution spec?▼

The required frontmatter fields for a sequential execution spec include mode, spec-version, playwright, and frontend-design. These fields are auto-injected to guide implementation and validation.

How do I generate a structured task list with explicit file changes and tests?▼

To generate a structured task list with explicit file changes and tests, summarize your conversational planning output. The spec creation process structures these tasks sequentially, embedding validation steps directly into the execution plan.

Can I use parallel sub-agents when running sequential task specs?▼

No, you cannot use parallel sub-agents when running sequential task specs. The spec strictly enforces linear order across all tasks to ensure a single-threaded build workflow without parallel execution.

When should I not use a linear spec for task planning?▼

You should not use a linear spec for task planning if your workflow requires parallel sub-agents or multi-session execution. This approach is designed specifically for single-session tasks requiring strict sequential order.

Related Skills

Explore More Software Engineering Skills→
gooseworks-aigooseworks-ai
1.1k

brainstorming-partner

Facilitate collaborative brainstorming sessions with idea generation and clarifying questions.

Official
Advanced
a2musa2mus

speckit-implement

Execute task breakdowns to implement features and tests with TDD.

Community
Advanced
AustinZ21AustinZ21
4

speckit-implement

Execute spec-kit implementation task plans with dependency and checklist validation.

Community
Advanced
brandon-frysliebrandon-fryslie
4

hire-a-minion

Spawn a parallel Claude instance in a tmux session for concurrent task execution.

Community
Intermediate