skills.rest
dotCMS
dotCMSOFFICIAL
Explore all skills by this author →
WebsiteGitHub

speckit-specify-fix

Creates defect-framed bug-resolution specifications from issue reports for the dotCMS spec-kit workflow.

950|482|Updated Mar 15, 2012
Search Tags:#specification#software maintenance#Bug Fix#dotcms#issue template#regression risk#spec-Kit
One-click install
npx skills add https://github.com/dotCMS/core --skill speckit-specify-fix
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-specify-fix
Source: https://github.com/dotCMS/core/tree/main/.claude/skills/speckit-specify-fix
Command: npx skills add https://github.com/dotCMS/core --skill speckit-specify-fix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When fixing bugs in dotCMS, teams need a structured specification that captures the problem, reproduction steps, root-cause hypothesis, fix scope, and regression risk before any code is written. This Skill converts a raw bug report or issue description into a defect-framed specification that feeds directly into the spec-kit plan, tasks, and implement phases.

Core Features & Use Cases

  • Issue Spec Generation: Parses a bug report and fills the dotCMS issue template with problem statement, reproduction steps, expected vs actual behavior, and severity.
  • Bounded Fix Scoping: Defines fix scope with explicit non-goals, regression risk assessment, and measurable acceptance criteria tied to the reproduction.
  • Quality Validation: Generates a requirements checklist and iterates on the spec, flagging up to three clarification questions when details are missing.
  • Use Case: A developer pastes a GitHub issue describing a broken content search filter; the Skill creates a feature branch, writes the issue spec at the spec file path, validates it against the checklist, and hands off to /speckit-plan for legacy impact and ADR alignment review.

Quick Start

Run the speckit-specify-fix skill and paste the bug report or issue title with reproduction steps to generate a defect specification.

Frequently Asked Questions about speckit-specify-fix

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

FAQPage Schema
How do I write a bug fix specification from a GitHub issue?▼

Paste the issue title and reproduction details as input, and the Skill parses the report into a structured spec covering problem statement, reproduction steps, root-cause hypothesis, fix scope, and acceptance criteria. Missing details are flagged with clarification markers.

What is the difference between speckit-specify and speckit-specify-fix?▼

speckit-specify-fix is the defect-framed variant for fixing existing behavior, using the dotCMS issue template with sections for reproduction and regression risk. Use the standard speckit-specify when the work is a new feature rather than a bug fix.

Does speckit-specify-fix require a spec-kit project structure?▼

Yes, it requires a .specify directory containing the create-new-feature.sh script, the spec-issue-template.md template, and the constitution.md memory file. Without this structure the branch creation and template seeding steps cannot run.

Can this skill write or modify code to fix the bug?▼

No, it only scopes the fix by producing the specification document. Code changes happen later in the /speckit-implement phase, and architectural decisions are deferred to the plan phase as proposed ADRs.

What happens when the bug report lacks reproduction details?▼

The Skill marks gaps with up to three [NEEDS CLARIFICATION] markers, then presents numbered questions with suggested answers and waits for your response before finalizing the spec.

Related Skills

Explore More Software Engineering Skills→
cslsoftwarescslsoftwares

quality-bug-triage

Convert informal bug reports into structured tickets with severity and reproduction steps.

Community
Intermediate
notquenotque
415

adr-consultation

Coordinate parallel reviewers to assess ADRs and enforce blocking gates.

Community
Advanced
microsoftmicrosoft
35

setting-up-constitution

Create or update a project constitution codifying migration principles and governance constraints.

Official
Advanced
chohra-medchohra-med
28

spec-harness-tickets

Convert ticket tracker issues and ad-hoc plans into structured spec documents.

Community
Advanced