speclet-draft

Draft collaborative feature plans with clarifying questions to .speclet/draft.md.

Updated Jan 9, 2026
One-click install
npx skills add https://github.com/danielcastro-dev/speclet --skill speclet-draft
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speclet-draft
Source: https://github.com/danielcastro-dev/speclet/tree/main/.opencode/skill/speclet-draft
Command: npx skills add https://github.com/danielcastro-dev/speclet --skill speclet-draft

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams draft feature plans by generating a collaborative draft and clarifying questions, reducing ambiguity early.

Core Features & Use Cases

  • Asks 3-5 clarifying questions with lettered options for quick responses
  • Creates a structured draft document at .speclet/draft.md
  • Identifies scope, non-goals, and affected files
  • Breaks down the feature into right-sized stories
  • For tickets: reads existing ticket context and refines into an actionable draft

Quick Start

Describe your feature or ticket context in plain language and I will generate a clarifying-question draft and save it to .speclet/draft.md.

Frequently Asked Questions about speclet-draft

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

FAQPage Schema
How do I draft a feature plan with clarifying questions to reduce scope ambiguity?

Drafting a feature plan with clarifying questions is done by generating a collaborative draft that asks 3-5 targeted questions with lettered options. This reduces ambiguity early and outputs the structured plan to .speclet/draft.md.

How does ticket context refine into an actionable feature draft?

Ticket context refines into an actionable feature draft when the tool operates in Ticket Mode. By referencing a TICKET-N, it reads existing context to shape the draft, identifying scope, non-goals, and affected files automatically.

What is the best way to break down a feature draft into right-sized stories?

The best way to break down a feature draft into right-sized stories is by using a structured draft document. It processes your plain language feature description to identify scope and non-goals, then outputs actionable stories to .speclet/draft.md.

Do I need existing tickets to generate a feature draft with clarifying questions?

You do not need existing tickets to generate a feature draft. The tool uses Normal Mode to shape the draft from your plain language input, asking 3-5 clarifying questions with lettered options for quick responses.

Can I define non-goals and affected files when planning a feature workflow?

You can define non-goals and affected files when planning a feature workflow. The draft generation process explicitly identifies scope boundaries and affected files, outputting this structured information to the .speclet/draft.md file.

Why use clarifying questions with lettered options for feature planning?

Using clarifying questions with lettered options for feature planning enables quick, structured responses. It generates a collaborative draft that defines scope and outcomes early, reducing ambiguity before development begins.