keystone:spec

Document task intent and acceptance criteria before work begins.

42|3|Updated May 31, 2026

Search Tags:#code quality #task management #specification #acceptance criteria #team alignment

Ready to run

npx skills add https://github.com/tacoda/keystone --skill keystone-spec

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: keystone:spec
Source: https://github.com/tacoda/keystone/tree/main/internal/framework/scaffold/templates/charter/skills/keystone-spec
Command: npx skills add https://github.com/tacoda/keystone --skill keystone-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that the intent and acceptance criteria for a unit of work are captured and documented at the start of every task, preventing scope drift and ensuring that all stakeholders are aligned.

Core Features & Use Cases

Capture Intent: Documents the desired outcome before any work begins, ensuring clarity and direction.
Acceptance Criteria: Defines what constitutes "done" for a task, reducing misunderstandings and rework.
Use Case: When beginning a new task, use the keystone:spec skill to write down the acceptance criteria, ensuring all team members are on the same page.

Quick Start

Run 'keystone spec' to start capturing intent and acceptance criteria for your task.

Frequently Asked Questions about keystone:spec

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

FAQPage Schema

How do I define acceptance criteria to prevent scope drift in task management?▼

Defining acceptance criteria requires documenting the desired outcome and task intent before work begins, ensuring stakeholders share a clear definition of done. This structured approach prevents scope drift and reduces rework.

What is the best way to capture task intent for team alignment?▼

The best way to capture task intent for team alignment is to document the desired outcome at the start of a unit of work. This ensures clear communication and direction, keeping all team members focused on the same goal.

How do I write clear specifications for a unit of work before execution?▼

Writing clear specifications for a unit of work requires a structured approach to documentation that captures intent and acceptance criteria upfront. This ensures clear communication and alignment before any task execution begins.

Does capturing acceptance criteria work for any task management context?▼

Yes, capturing acceptance criteria is applicable to any task where understanding the desired outcome is crucial. It requires a structured approach to documentation and a commitment to collaborative development across contexts.

Why does my team experience scope drift during task execution?▼

Your team experiences scope drift during task execution when intent and acceptance criteria are not captured and documented at the start of a task. Without this initial alignment, stakeholder misunderstandings lead to rework.