socratic-spec-authoring

Capture task requirements in spec.md through Socratic questions and approval gating.

Updated Mar 7, 2026
One-click install
npx skills add https://github.com/alexization/git-ranker-workflow --skill socratic-spec-authoring
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: socratic-spec-authoring
Source: https://github.com/alexization/git-ranker-workflow/tree/main/.codex/skills/socratic-spec-authoring
Command: npx skills add https://github.com/alexization/git-ranker-workflow --skill socratic-spec-authoring

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the careful specification and approval process for task work by capturing stakeholder requirements in spec.md, guiding clarification logs, and locking the intake data until explicit user approval.

Core Features & Use Cases

  • Captures request, problem, goals, non-goals, constraints, and acceptance criteria via structured, question-based spec.
  • Maintains a Socratic Clarification Log with Q:, A:, and Status: markers for traceable decisions.
  • Prevents premature work by locking task.json intake after explicit user approval and moving to the next phase only when consent is obtained.
  • Supports iterative clarifications and dynamic updates to the spec as questions arise.

Quick Start

Initiate a Socratic specification session for a new task and lock the intake after the user explicitly approves.

Frequently Asked Questions about socratic-spec-authoring

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

FAQPage Schema
How do I lock task intake until explicit approval is given?

To lock task intake until explicit approval, this Socratic approval workflow records problem, goals, constraints, and acceptance criteria in spec.md, gating phase transitions so progression only occurs after user consent.

What is a Socratic clarification log for task specification?

A Socratic clarification log for task specification captures Q:, A:, and Status: markers to ensure traceable decisions during the intake process, dynamically updating spec.md as requirements are refined through targeted questions.

How do I prevent premature work on a task before requirements are approved?

Preventing premature work requires a confirmation gating mechanism that locks task.json intake, ensuring no phase progression happens until the user explicitly approves the comprehensive task spec.

Can I iteratively update task constraints and non-goals during the spec process?

Yes, you can iteratively update task constraints and non-goals during the Socratic specification session. The workflow supports dynamic updates to spec.md as new questions arise and requirements evolve.

Does this task intake workflow require dependencies to capture acceptance criteria?

No dependencies are required to capture acceptance criteria. The Socratic specification process operates independently, using structured question-based intake to assemble problem statements, goals, and constraints directly into spec.md.