jumppad-labs

jumppad-labs/spektacular

Command

Execute an approved Plan to implement the feature.

jumppad-labs/spektacular

Command

Search, contribute to, or update the project's knowledge base.

jumppad-labs/spektacular

Command

Create a new Specification for a feature.

jumppad-labs/spektacular

Command

Create a new Plan from an approved Specification.

jumppad-labs/spektacular

Skill Claude CodeCodex

Execute an approved Plan to implement the feature.

jumppad-labs/spektacular

Skill Claude CodeCodex

Search, contribute to, or update the project's knowledge base.

jumppad-labs/spektacular

Skill Claude CodeCodex

Create a new Specification for a feature.

jumppad-labs/spektacular

Skill Claude CodeCodex

Create a new Plan from an approved Specification.

jumppad-labs/spektacular

Settings file Claude Code

Agent settings declaring 20 allowed tools.

jumppad-labs/spektacular

MCP server Claude CodeCodexCursor +2

MCP server "tessl" as configured in jumppad-labs/spektacular. Launched with tessl mcp start.

jumppad-labs/spektacular

Instructions file CodexOpenCode

Instructions for jumppad-labs/spektacular, covering agent rules, memory & context, spec-worthy discussion recognition, historical artifacts: specs and plans as archaeology and presenting drafts and confirmations.

jumppad-labs/spektacular

Instructions file

Instructions for jumppad-labs/spektacular, a project described as: Spec-driven development for AI coding agents. Spektacular helps you to generate specifications, the plan, and finally generate the code. Agent-agnostic and pluggable: Claude Code, Bob, Codex.

jumppad-labs/spektacular

Agent

When you have drafted substantial content for the user to review — an architecture write-up, a set of options, a written section, a summary, a plan or spec excerpt — always present that draft as normal, readable chat text first, in full. Never embed the draft itself inside a structured yes/no or multiple-choice dialog…

jumppad-labs/spektacular

Agent

In this repository, treat every file under .spektacular/specs/ and .spektacular/plans/ as a historical, archaeological record. Each one describes the intent behind a past change — why something was proposed, what was in scope at that moment, and how the author framed the problem. None of them are a description of what…

jumppad-labs/spektacular

Agent

While working — debugging, reading code to understand how something works, making a non-obvious choice — watch for the moment you surface something durable and non-obvious: a convention inferred from code that isn't written down anywhere, a gotcha hit while debugging, the reasoning behind a choice that wasn't the…

jumppad-labs/spektacular

Agent

In this repository, do not persist anything to your per-user, per-machine memory store. When you would normally write to it — a learning, convention, gotcha, project fact, user preference, or anything else worth remembering between sessions — route the write through the spek-knowledge skill instead. The skill handles…

jumppad-labs/spektacular

Agent

During an open-ended discussion (diagnostics, brainstorming, exploratory back-and-forth), watch for the moment it produces something substantial enough to be worth capturing as a specification — multiple requirements mentioned, a scoped decision reached, or a feature described in enough detail that it could be built…

jumppad-labs/spektacular

Command

Run the {{skill}} skill.