light-spec

Generate a structured light spec from a Linear issue for VBW planning ingestion.

6|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/withpiper/pipekit --skill light-spec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: light-spec
Source: https://github.com/withpiper/pipekit/tree/main/skills/01-light-spec
Command: npx skills add https://github.com/withpiper/pipekit --skill light-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Draft a structured light spec for a Linear issue, ready for VBW planning ingestion, bridging the gap between raw brainstorms and full VBW PLAN.md files.

Core Features & Use Cases

  • Create a lightweight, VBW-ingestible spec from a new or existing Linear issue.
  • Include inputs, phase context, decision discipline, and acceptance criteria to enable deterministic planning.
  • Use case: given issue PROJ-123, generate a light spec that can feed VBW planning.

Quick Start

Invoke /light-spec with an issue ID or a description of the idea to generate a VBW-ingestible light spec.

Frequently Asked Questions about light-spec

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

FAQPage Schema
How do I draft a light spec for a Linear issue to feed VBW planning?

Drafting a light spec for a Linear issue involves invoking the automation with an issue ID or idea description. It generates a VBW-ingestible spec covering inputs, context, decision points, and acceptance criteria for deterministic planning.

What is a light spec and how does it support deterministic task decomposition?

A light spec is a structured document bridging raw brainstorms and full VBW PLAN files. It cleanly separates WHAT from HOW, enforces explicit decisions, and marks TBDs to support deterministic task decomposition in planning.

Can I use light-spec to generate planning inputs from an existing Linear issue?

Yes, you can generate a lightweight spec from an existing Linear issue. Provide the issue ID to the automation, and it will structure the issue's inputs, phase context, and acceptance criteria for VBW planning ingestion.

What is the best way to structure issue specs for VBW planning ingestion?

The best way to structure issue specs for VBW planning is to explicitly separate WHAT from HOW, define required inputs, and list acceptance criteria. This structured light spec format enables deterministic planning automation.

How do I handle decision points and missing context when creating a Linear issue spec?

When creating a Linear issue spec, the automation enforces explicit decision discipline and marks necessary missing context as TBD. This ensures planning ingestion captures all required phase context without blocking on incomplete inputs.