speck-help

# Speck Workflow Skill

**Purpose**: Automatically interpret Speck specification artifacts (spec.md,
plan.md, tasks.md) and answer natural language questions about features without
requiring explicit slash commands.

**Activation**: This skill activates when users ask questions about Speck
features, mention file types (spec/plan/tasks), or reference Speck concepts
(requirements, user stories, architecture, etc.).

**Scope**: Read-only operations. This skill NEVER modifies files. For creating
or updating files, guide users to appropriate slash commands.

**Additional Resources**:

- **[reference.md](reference.md)** - Detailed interpretation rules, file states,
  error formats
- **[examples.md](examples.md)** - Usage examples showing skill in action
- **[workflows.md](workflows.md)** - Advanced features (multi-repo, worktrees,
  session handoff)

---

## Core Capabilities

### 1. Feature Discovery

When users reference features, use **three-tier matching** to locate the correct
feature directory:

#### Tier 1: Exact Match (Highest Priority)

- Direct directory name match: `specs/005-speck-skill/`

#### Tier 2: Numeric Prefix Match (High Priority)

- User provides feature number (e.g., "005", "5", "feature 003")
- Zero-pad numbers to 3 digits: "5" → "005"
- Match against pattern: `specs/NNN-*/`

#### Tier 3: Fuzzy/Substring Match (Lower Priority)

- User provides partial name (e.g., "skill", "auth", "plugin")
- Filter by case-insensitive substring match
- If multiple matches, ask for clarification

**Disambiguation**: When multiple features match, check conversation context
first. If ambiguous, ask: "Did you mean: 003-user-auth or 012-auth-tokens?"

**Error Handling**: List all available features, use Levenshtein distance for
typo suggestions, explain matching rules.

**Worktree Context**: Worktrees share the same `specs/` directory as main
repository. Feature discovery works identically in worktrees and main repo.

---

### 2. Template References

Speck uses templates