gen-spec

Generate and register formal specifications under specs/ before coding.

Updated Jul 2, 2026

Search Tags:#workflow #documentation #requirements #validation #feature-spec #spec-generation #spec-conventions

Ready to run

npx skills add https://github.com/SamyakJhaveri/loam --skill gen-spec-samyakjhaveri

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gen-spec
Source: https://github.com/SamyakJhaveri/loam/tree/main/seed/.claude/skills/gen-spec
Command: npx skills add https://github.com/SamyakJhaveri/loam --skill gen-spec-samyakjhaveri

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Drafting incomplete or ambiguous specifications leads to scope drift and costly rework. This Skill enforces a specs-first workflow, guiding you to write structured specs before implementation and to validate and register them in the project.

Core Features & Use Cases

Guided spec lifecycle: scope validation, drafting, inline validation, review, and registration.
Creates specs under specs/ with naming conventions and links to related ADRs or design docs.
Validates structure, references, acceptance criteria, naming, and constraints to ensure verifiability.
Supports ADR-style decision records for hard-to-reverse design choices and documented trade-offs.

Quick Start

Invoke the gen-spec workflow with the feature or component name to generate and register a new specification.

Frequently Asked Questions about gen-spec

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

FAQPage Schema

How do I prevent scope drift when drafting feature specifications?▼

To prevent scope drift, draft formal specifications before coding to validate scope, acceptance criteria, and constraints. This specs-first workflow enforces structured templates and naming consistency to ensure verifiability.

What is the best way to document hard-to-reverse design choices in a spec workflow?▼

Documenting hard-to-reverse design choices in a spec workflow uses ADR-style decision records to capture trade-offs. These records link directly within specifications to provide context and rationale for architectural constraints.

How do I validate acceptance criteria and references before registering a new API spec?▼

Validating acceptance criteria and references before registering a new API spec requires inline validation during the drafting phase. This ensures structure, naming consistency, and constraint verifiability before the spec is registered.

Does this spec generation workflow support linking to existing ADRs and design docs?▼

Yes, this spec generation workflow supports linking to existing ADRs and design docs. It creates specifications under a dedicated directory and automatically references related architecture decision records for context.

What naming conventions are enforced when creating specification documents?▼

When creating specification documents, naming conventions are enforced to maintain consistency across the project. The workflow validates file names and references during the inline validation phase before final registration.