Managing Specifications

Manage specification lifecycles with draft, active, and completed folders.

20|2|Updated Jul 8, 2025
One-click install
npx skills add https://github.com/jeanluciano/quaestor --skill managing-specifications
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Managing Specifications
Source: https://github.com/jeanluciano/quaestor/tree/main/src/quaestor/skills/managing-specifications
Command: npx skills add https://github.com/jeanluciano/quaestor --skill managing-specifications

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It provides end-to-end management of specifications from draft to completion, with automatic progress tracking.

Core Features & Use Cases

  • 3-active-spec limit with automatic enforcement
  • Progress tracking from checkboxes
  • Lifecycle transitions: draft → active → completed
  • Metadata updates and reporting

Quick Start

Create or view specs: "Create a spec for X" or "Show active specs" or "Activate spec-feature-003".

Frequently Asked Questions about Managing Specifications

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

FAQPage Schema
How do I manage specifications through their complete lifecycle?

Managing specifications through their lifecycle involves moving specs from draft to active to completed status. The system automatically enforces a three-folder structure, limits you to three active specs at once, and updates timestamps and progress tracking based on completion checkboxes in your spec documents.

What validation rules apply to specification metadata and frontmatter?

Specification metadata validation enforces consistency across frontmatter fields, dependencies, risks, acceptance criteria, and test scenarios. The system prevents invalid state transitions and maintains metadata integrity throughout the lifecycle, rejecting specs that fail validation before allowing status changes.

Can I track progress automatically on active specifications?

Progress tracking on active specifications happens automatically through checkboxes within your spec documents. The system calculates and updates progress status in real time, allowing you to monitor completion across all three concurrent active specs without manual updates.

What happens when I exceed the three active specification limit?

The system enforces a maximum of three active specs at any time. When you attempt to activate a fourth spec, the enforcement blocks the transition, requiring you to complete or move an existing active spec to completed status first.

How do specification dependencies and risks get validated?

Dependencies and risks in specification frontmatter are validated for consistency and correctness during status transitions. The system checks that all declared dependencies exist, risks are properly documented, and acceptance criteria align with test scenarios before allowing specs to move through lifecycle stages.