goal-from-spec

Generate a /goal command pointing to a feature spec directory.

11|Updated Sep 5, 2025
One-click install
npx skills add https://github.com/thrawn01/claude-dotfiles --skill goal-from-spec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: goal-from-spec
Source: https://github.com/thrawn01/claude-dotfiles/tree/main/skills/goal-from-spec
Command: npx skills add https://github.com/thrawn01/claude-dotfiles --skill goal-from-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill emits a /goal command pointed at a feature directory containing prd.md, tech-spec.md, and optionally user-stories.md. It enables launching feature implementations directly from user input by referencing the feature's spec location.

Core Features & Use Cases

  • Identify the feature directory path. If ambiguous, ask once; otherwise read it from the conversation.
  • Check which of prd.md, tech-spec.md, and user-stories.md exist in that directory.
  • Emit the command using the template below in a fenced code block, with no commentary after.
  • If user-stories.md is present, append a constraint that each user story must be satisfied with a passing test.

Quick Start

Paste the feature directory path to generate the /goal command and receive it ready in a fenced code block.

Frequently Asked Questions about goal-from-spec

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

FAQPage Schema
How do I generate a slash command from a feature spec?

To generate a slash command from a feature spec, provide the feature directory path containing your prd.md and tech-spec.md files, and the tool will emit a formatted command pointing to that directory.

How does the goal command handle user-stories.md during feature implementation?

The goal command handles user-stories.md by appending a constraint that each user story must be satisfied with a passing test, ensuring test coverage when the file is present in the feature directory.

What is the best way to launch feature implementation from a prd.md file?

The best way to launch feature implementation from a prd.md file is to reference its directory path, allowing the system to automatically derive guidance from the PRD and tech-spec files to build the command.

Do I need a specific directory structure to run a feature spec command?

You need a feature directory structure like docs/features/<name>/ where your prd.md, tech-spec.md, and optionally user-stories.md files reside to successfully run the feature spec command.

What happens if the feature directory path is ambiguous when building the command?

If the feature directory path is ambiguous when building the command, the system will ask once for clarification; otherwise, it reads the path directly from the conversation context.

Are there limitations on the output format for the emitted goal command?

A limitation on the output format is that the emitted goal command must strictly follow the template exactly within a fenced code block, with absolutely no commentary provided afterward.