playbooks

home / skills / jeremylongshore / claude-code-plugins-plus-skills / spec-writing

spec-writing skill

/plugins/community/sprint/skills/spec-writing

This skill helps you craft precise sprint specifications and testing configurations by guiding scope and requirements in spec-writing.

npx playbooks add skill jeremylongshore/claude-code-plugins-plus-skills --skill spec-writing

Review the files below or copy the command above to add this skill to your agents.

Files (4)
SKILL.md
1.2 KB
---
name: spec-writing
description: |
  Execute this skill should be used when the user asks about "writing specs", "specs.md format", "how to write specifications", "sprint requirements", "testing configuration", "scope definition", or needs guidance on creating effective sprint specifications for agentic development. Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.
allowed-tools: Read
version: 1.0.0
author: Damien Laine <[email protected]>
license: MIT
---

# Spec Writing

## Overview

This skill provides automated assistance for the described functionality.

## Prerequisites

- Appropriate file access permissions
- Required dependencies installed

## Instructions

1. Invoke this skill when the trigger conditions are met
2. Provide necessary context and parameters
3. Review the generated output
4. Apply modifications as needed

## Output

The skill produces structured output relevant to the task.

## Error Handling

See `{baseDir}/references/errors.md` for comprehensive error handling.

## Examples

See `{baseDir}/references/examples.md` for detailed examples.

## Resources

- Project documentation
- Related skills and commands

Overview

This skill helps you create clear, testable sprint specifications and configuration-ready requirements for agentic development. I generate structured spec templates, scope definitions, acceptance criteria, and basic test configuration suggestions so teams can move from idea to implementation faster. Use it to standardize handoffs between product, engineering, and QA.

How this skill works

Provide the feature goal, user persona, constraints, and any existing artifacts; I produce a spec that includes purpose, scope, user stories, success metrics, acceptance tests, and a minimal test configuration. I flag ambiguous requirements, highlight dependencies, and output in a concise, copy-pasteable format for sprint planning. You can iterate by supplying clarifications or alternative constraints and I will refine the spec.

When to use it

  • Drafting sprint-level specs for new features or integrations
  • Converting product requests into implementation-ready acceptance criteria
  • Defining test configurations for automated or manual QA
  • Scoping MVP vs full-feature work to plan sprint capacity
  • Preparing clear handoffs between design, engineering, and QA

Best practices

  • Start with a single-sentence goal and 1–3 measurable success metrics
  • Limit scope per spec to what fits comfortably in one sprint
  • Always include explicit acceptance criteria and at least one test case per criterion
  • Call out dependencies, permissions, and environment needs up front
  • Iterate specs with concise clarifying questions rather than broad rewrites

Example use cases

  • Turn a product ticket into a sprint-ready spec with user stories and acceptance tests
  • Create a testing configuration outline (environments, data needs, steps) for an API change
  • Reduce an ambiguous request into a scoped MVP and backlog follow-ups
  • Generate QA checklists from acceptance criteria for manual verification
  • Produce a one-page scope summary to align stakeholders before sprint planning

FAQ

What inputs produce the best spec output?

Provide the goal, target user, constraints, desired metrics, and any existing wireframes or endpoints; I use these to create precise acceptance criteria and test cases.

Can you create test configurations for CI/CD pipelines?

Yes. I can suggest minimal environment setups, sample test data, and test steps suitable for CI integration, but you should adapt environment-specific details to your pipeline.