ln-spec

Organize creation, updates, and validation of project specifications.

7|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/hashintel/brunch --skill ln-spec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ln-spec
Source: https://github.com/hashintel/brunch/tree/main/.agents/skills/ln-spec
Command: npx skills add https://github.com/hashintel/brunch --skill ln-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill assists in crystallizing shared understanding into structured specifications, enabling clear documentation and decision tracking in project workflows.

Core Features & Use Cases

  • Specification Drafting: Guides users in creating comprehensive project specifications with defined sections.
  • Workflow Guidance: Provides step-by-step instructions for specification development and updates.
  • Use Case: A product manager updates a project spec when requirements change, ensuring all details are documented systematically.

Quick Start

Initiate a spec document for a new feature and add core requirements and assumptions in the designated sections.

Frequently Asked Questions about ln-spec

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

FAQPage Schema
How do I write project specifications for complex development teams?

Writing project specifications for complex development teams requires systematically documenting requirements, assumptions, decisions, and invariants to ensure clarity and traceability across the workflow.

What is the best way to maintain requirements traceability when updating a project spec?

Maintaining requirements traceability when updating a project spec involves following structured workflow guidance to systematically document requirement changes and track decisions across the development team.

How do I validate project specifications to ensure all details are systematically documented?

Validating project specifications involves applying systematic spec management practices to review defined sections, ensuring all documented requirements, assumptions, and invariants maintain clarity and consistency.

Can I use this specification management approach for tracking decisions and assumptions in product management?

Yes, specification management for product management supports tracking decisions and assumptions by organizing them into structured documentation with defined sections, ensuring shared understanding across project workflows.

What sections should I include when drafting a comprehensive project specification?

Drafting a comprehensive project specification should include defined sections for core requirements, assumptions, decisions, and invariants, guided by best practices for systematic spec management.

When do I need systematic spec management for my project documentation?

You need systematic spec management for project documentation when working on complex projects that require crystallizing shared understanding into structured specifications with clear traceability across development teams.