Generate lean feature specifications defining WHAT and WHY with linked external docs.
npx skills add https://github.com/arittr/spectacular --skill writing-specs
Please help me install this Agent Skill. Skill: writing-specs Source: https://github.com/arittr/spectacular/tree/main/skills/writing-specs Command: npx skills add https://github.com/arittr/spectacular --skill writing-specs
This Skill eliminates the common pitfalls of overly detailed, hard-to-maintain specifications that mix requirements with implementation details. It ensures your feature specifications are concise, focused on "WHAT" and "WHY," and easily digestible, preventing spec drift and inefficiency.
spec.md document, ensuring all requirements are captured without getting bogged down in implementation details, which are handled by other Skills./spectacular:spec "admin dashboard with real-time analytics"
cat specs/a1b2c3-refactor-components/spec.md
High-intent search queries and answers about installing and using this skill.
Feature specifications should define WHAT to build and WHY, not HOW. Lean specs capture Problem Statement, Functional and Non-Functional Requirements, Architecture, Dependencies, Integration Points, and Acceptance Criteria while avoiding implementation details, code examples, and success metrics. This keeps specs concise, maintainable, and focused on requirements rather than solution approach.
A comprehensive spec includes Problem Statement, Functional and Non-Functional Requirements, Architecture, Dependencies, Integration Points, and Acceptance Criteria. Link to external documentation rather than embedding examples, and reference project constitutions for architectural rules and mandatory patterns to ensure consistency and avoid duplication.
Generate feature specifications after brainstorming sessions to draft a comprehensive yet lean spec document. This ensures all requirements are captured without getting bogged down in implementation details, which are handled separately. Specs serve as the bridge between ideation and development planning.
Specification drift occurs when specs mix requirements with implementation details and become hard to maintain. Keep specs lean by linking to external documentation instead of embedding examples, focusing on WHAT and WHY, and following established architectural constitutions and planning standards consistently across projects.
Yes. Integrating project constitutions into specs automatically references architectural rules and mandatory patterns, ensuring consistency across features and preventing duplication. This approach standardizes how specs are structured and what architectural decisions are documented.
Lean specs define WHAT to build and WHY through requirements and architecture, avoiding implementation plans, code examples, or success metrics. Implementation plans are downstream artifacts that translate specs into concrete steps. Separating these concerns keeps specs focused, reusable, and easier to maintain.
silaslopes100Guide structured brainstorming sessions to refine project ideas into validated product briefs.
kgadekPlan and orchestrate a Specification-Driven Development workflow to produce a complete SPEC.
rhussCreate and maintain a project constitution defining standards and validating specs.
abhishekchoudhariCreate job stories in a When-I-want-so format with acceptance criteria.