adlc-spec-specify

Translate natural language feature prompts into ADLC specification artifacts.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/chaimt/GarminShabbatMode --skill adlc-spec-specify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adlc-spec-specify
Source: https://github.com/chaimt/GarminShabbatMode/tree/main/.cursor/skills/adlc-spec-specify
Command: npx skills add https://github.com/chaimt/GarminShabbatMode --skill adlc-spec-specify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ThisSkill automates the end-to-end process of turning natural language feature prompts into formal software specifications within the ADLC workflow. It orchestrates mission brief collection, decision-making, branch creation, and specification writing so teams can plan and implement features with clarity and guardrails.

Core Features & Use Cases

  • Mission Brief Generation: Extract goals, success criteria, and constraints from user input to define the scope of the feature.
  • Branch & Spec Scaffolding: Create a feature branch and generate a structured specification file from templates to begin planning.
  • Specification Authoring: Compile assumptions, user scenarios, testing criteria, and acceptance criteria into a complete spec document.
  • Quality & Clarification Loop: Run a reflexive quality checklist, surface uncertainties, and manage clarifications to keep scope aligned.

Quick Start

Provide a feature description after /spec.specify to begin the specification workflow.

Frequently Asked Questions about adlc-spec-specify

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

FAQPage Schema
How do I turn a natural language feature prompt into a formal software specification?

To turn a natural language feature prompt into a formal software specification, provide your feature description to initiate the workflow that extracts goals, success criteria, and constraints into a testable SPEC file ready for review.

What is the ADLC workflow for feature specification and planning?

The ADLC workflow for feature specification is an end-to-end process that captures a mission brief, scaffolds a feature branch, and authors a structured specification document complete with assumptions, user scenarios, and acceptance criteria.

How do I generate a feature branch and spec scaffolding from a mission brief?

You generate a feature branch and spec scaffolding by inputting your feature goals, which automatically creates a structured specification file from templates and establishes the branch to begin planning.

Can I automate quality checks and clarifications for my feature specification?

Yes, you can automate quality checks and clarifications for your feature specification by running a reflexive quality checklist that surfaces uncertainties and manages scope alignment through targeted clarifications.

What's the best way to compile user scenarios and acceptance criteria into a spec document?

The best way to compile user scenarios and acceptance criteria into a spec document is using an AI-assisted workflow that orchestrates assumptions, testing criteria, and constraints into a complete, testable specification artifact.

Why do I need to define success criteria and constraints before writing a feature spec?

You need to define success criteria and constraints before writing a feature spec to ensure the generated specification captures the correct scope, maintains compliance with the ADLC workflow, and produces formal, testable acceptance scenarios.