spec

Name: spec
Availability: InStock
Author: CasaPerks

Convert Jira engineering tickets into build-ready feature specifications.

Updated Aug 23, 2026

Search Tags:#workflow automation #spec writing #acceptance criteria #jira #feature flags #architecture sketch #test spec

Ready to run

npx skills add https://github.com/CasaPerks/casaflow --skill spec-casaperks

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec
Source: https://github.com/CasaPerks/casaflow/tree/main/team/skills/spec
Command: npx skills add https://github.com/CasaPerks/casaflow --skill spec-casaperks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns a vague engineering ticket into a build-ready feature specification that developers and Claude can align on before any code is written.

Core Features & Use Cases

Guided feature-spec interview: Helps you write a precise spec covering summary, acceptance criteria, non-goals, test plan, and an architecture sketch.
Comprehension-gated workflow: Forces clarity through red-flag checks (e.g., vague criteria, missing failure cases, missing architecture, zero open questions) before proceeding.
Optional Jira context pre-seeding: When Jira is configured, it can fetch ticket context and pre-seed the spec, and it routes bug tickets to the appropriate kickoff flow.

Quick Start

Run /casaflow:spec with your Jira ticket ID to start the guided feature-spec interview.

Frequently Asked Questions about spec

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

FAQPage Schema

How do I turn Jira tickets into build-ready feature specs?▼

You can turn Jira tickets into build-ready feature specs by running a guided interview process that extracts acceptance criteria, non-goals, test plans, and architecture sketches, automatically pre-seeding context from your Jira ticket ID.

What is needed to write acceptance criteria with non-goals and test specs?▼

Writing complete acceptance criteria with non-goals and test specs requires an interview-driven workflow that enforces strict validation checks for testability, failure cases, and architecture completeness before allowing the specification to proceed.

How do I validate feature flags and architecture completeness before implementation?▼

You validate feature flags and architecture completeness by applying a comprehension-gated workflow that performs red-flag checks for vague criteria, missing failure cases, and zero open questions to ensure full spec clarity.

Can I use this spec writing workflow for bug tickets in Jira?▼

This spec writing workflow applies to feature, story, task, and improvement tickets, automatically routing bug tickets to the appropriate separate kickoff flow when Jira context is configured and fetched.

Does the spec writing process work without Jira configured?▼

The spec writing process works without Jira configured, but you lose the optional Jira context pre-seeding that automatically fetches ticket details to pre-populate the structured feature specification.