skills.rest
withpiper
withpiperOFFICIAL
Explore all skills by this author →
WebsiteGitHub

light-spec-revise

Apply only requested Spec Review Agent fixes to a Light Spec with diff previews.

6|Updated Apr 8, 2026
Search Tags:#linear#diff#spec#patch#revision#light-spec#agent-feedback
One-click install
npx skills add https://github.com/withpiper/pipekit --skill light-spec-revise
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: light-spec-revise
Source: https://github.com/withpiper/pipekit/tree/main/skills/02-light-spec-revise
Command: npx skills add https://github.com/withpiper/pipekit --skill light-spec-revise

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Close the feedback loop between Linear's Spec Review Agent and a published Light Spec by applying agent feedback incrementally, avoiding a full redraft.

Core Features & Use Cases

  • Selective patching: apply only the fixes the agent requested, leaving the rest unchanged.
  • Stalemate detection: identify when repeated verdicts address already-covered blockers and avoid unnecessary rewrites.
  • Diff previews: present surgical patches as diffs before applying them.
  • Traceability: maintain a clear link between agent feedback and applied changes.

Quick Start

Trigger a revision on a published Light Spec using the issue ID and review patch previews before applying any changes.

Frequently Asked Questions about light-spec-revise

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

FAQPage Schema
How do I apply agent feedback to a published Light Spec without a full rewrite?▼

To apply agent feedback without a full rewrite, patch the published Light Spec incrementally by applying only the fixes requested in the Spec Review Agent comment, leaving existing sections unchanged. You review diff previews and approve patches before they are applied.

How do I prevent unnecessary spec rewrites from repeated or stale agent verdicts?▼

To prevent unnecessary spec rewrites from stale agent verdicts, use stalemate detection to identify when repeated comments address already-covered blockers, avoiding redundant patches and maintaining traceability against the published spec.

Can I preview changes before applying patches to a Linear issue spec?▼

Yes, you can preview changes before applying patches to a Linear issue spec. The revision process presents surgical diff previews for each patch and requires explicit user approval before modifying the published spec.

How do I trace applied changes back to the original agent feedback?▼

You trace applied changes back to agent feedback by linking the Spec Review Agent comments directly to the surgical patches applied to the published Light Spec. This maintains a clear feedback loop without altering unaffected sections.

What is the best way to handle conflicting feedback on an existing Light Spec?▼

The best way to handle conflicting feedback on an existing Light Spec is to detect conflicting or stale agent comments during the patching process, ensuring only the most recent requested fixes are applied while preventing wholesale rewrites of the document.

Do I need a Linear issue ID to start revising a Light Spec?▼

Yes, you need a Linear issue ID. The revision process operates against the published Light Spec and its corresponding Linear issue to correctly identify and apply the fixes requested by the Spec Review Agent.

Related Skills

Explore More Product & Management Skills→
fixpoint-labsfixpoint-labs
2

fsd:implement-issue

Automate Linear issue implementation and review with GitHub PR management.

Official
Advanced
richfremrichfrem
5

spec-kitty-status

Track and verify Spec-Kitty workflow states with provenance-aware checks.

Community
Intermediate
alexei-lexxalexei-lexx

address-review-comments

Classify GitHub PR review comments and generate actionable fixes and replies.

Community
Advanced
marktodamarktoda

implement-cohesively

Implement approved spec rewrites across code, tests, and CI.

Community
Advanced