skills.rest
jschulte
jschulteCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

complete-spec

Resolve [NEEDS CLARIFICATION] markers in specifications via interactive Q&A sessions.

3|3|Updated Nov 16, 2025
One-click install
npx skills add https://github.com/jschulte/claude-plugins --skill complete-spec
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: complete-spec
Source: https://github.com/jschulte/claude-plugins/tree/main/stackshift/skills/complete-spec
Command: npx skills add https://github.com/jschulte/claude-plugins --skill complete-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ambiguous or incomplete specifications lead to rework, delays, and misaligned development. This skill interactively resolves all [NEEDS CLARIFICATION] markers, ensuring your project documentation is complete, unambiguous, and ready for implementation.

Core Features & Use Cases

  • Interactive Clarification: Engage in a Q&A session to fill missing details about features, UX/UI, behavior, and priorities.
  • Automated Spec Updates: Automatically update specifications in specs/ with user answers, removing clarification markers.
  • Use Case: After a gap analysis, you have a list of features needing more detail. Use this skill to systematically go through each item, asking the AI questions and having it update the specs in real-time, ensuring everyone is on the same page before coding begins.

Quick Start

Complete the specification for the 'Analytics Dashboard' feature, resolving all pending clarifications.

Frequently Asked Questions about complete-spec

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

FAQPage Schema
How do I resolve specification gaps before starting development?▼

Specification gaps are resolved through interactive clarification sessions that identify and address [NEEDS CLARIFICATION] markers in your specs. This skill conducts structured Q&A, collects answers, updates specification documents, and removes all ambiguity markers to produce complete, implementation-ready specs.

What's the best way to ensure specifications are complete and unambiguous?▼

Complete specifications require systematic clarification of missing details about features, UX/UI, behavior, and priorities. This skill automates that process by marking ambiguous areas, asking targeted questions, incorporating your answers directly into specs/, and delivering finalized documentation ready for implementation planning.

Can I update specifications automatically while clarifying requirements?▼

Yes. This skill updates specification documents in real-time as you answer clarification questions, removing [NEEDS CLARIFICATION] markers and integrating your responses directly into the specs. This ensures documentation stays synchronized with decisions and eliminates manual sync work.

How do I prepare specifications for the implementation phase?▼

Specifications are ready for implementation when all ambiguities are resolved and prioritized. This skill completes that preparation by resolving every clarification marker through interactive Q&A, finalizing all spec details, and generating prioritized implementation plans that downstream tools like /speckit.tasks and /speckit.implement can execute.

What happens if I skip specification clarification and move directly to coding?▼

Skipping clarification leads to rework, delays, and misaligned development because ambiguous specifications create conflicting interpretations. This skill prevents that by enforcing systematic resolution of all unclear points before development begins, ensuring the team shares a common understanding.

Does this work within a larger specification workflow?▼

Yes. This skill operates within stepwise specification refinement workflows, typically applied after gap analysis to resolve remaining clarification markers. It feeds complete, prioritized specs into downstream specification tools and implementation planning tools for coordinated development.

Related Skills

Pacheco95Pacheco95

speckit-clarify

Identify underspecified areas in feature specifications and encode clarifications into structured updates.

Community
Advanced
Ferreira-JeffersonFerreira-Jefferson
1

spec-creator

Generate a phase-driven specification package before code implementation.

Community
Advanced
t-miura-024t-miura-024

mt-sdd

Coordinate specification-driven development workflows from requirements analysis through implementation validation.

Community
Advanced
koki3141koki3141
2

readme-updater

Synchronize README updates from code changes using Git triggers.

Community
Intermediate