specifying-and-implementing

Converts conversations into structured specs and implements them via TDD workflows.

1|Updated Jul 17, 2026
One-click install
npx skills add https://github.com/dariovr1/sixth-sense --skill specifying-and-implementing-dariovr1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: specifying-and-implementing
Source: https://github.com/dariovr1/sixth-sense/tree/main/skills/specifying-and-implementing
Command: npx skills add https://github.com/dariovr1/sixth-sense --skill specifying-and-implementing-dariovr1

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Agreed-upon designs discussed in conversation often get lost or drift during implementation, and large multi-task features fail when errors in early tasks propagate uncaught. This Skill persists the design as a structured spec file and then implements it through disciplined TDD, verification, and review gates. ## Core Features & Use Cases - Spec Synthesis: Turns the current conversation into a structured specification (problem statement, user stories with verification commands, interfaces, testing decisions, risks) written to .sixth-sense/spec.md, with self-review, premortem risk analysis, and an optional second-opinion review pass. - Light Workflow: For small scopes (3 or fewer stories, ≤2 files each), runs a single continuous pass of TDD, typechecking, code review, and commit. - Heavy Workflow: For larger work, decomposes the spec into dependency-tracked tasks, dispatches parallel subagents with effort-based model routing, enforces per-task adversarial review gates, and tracks progress in a resumable ledger. - Use Case: After discussing a new caching feature with the AI, ask it to write the spec, then implement it — the Skill decomposes the stories, dispatches subagents for independent tasks, reviews each diff, and commits with a full-branch final review. ## Quick Start Turn our discussion about the caching feature into a spec and then implement it with TDD and code review.

Frequently Asked Questions about specifying-and-implementing

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

FAQPage Schema
How do I turn a conversation into a software specification?

The Spec phase synthesizes the current conversation into a structured document with problem statement, user stories, interfaces, and testing decisions, written to .sixth-sense/spec.md. Each user story must carry its own verification command, and a self-review plus premortem risk pass runs before the spec is presented.

How do I implement a large feature with multiple tasks using AI agents?

The Heavy Workflow decomposes the spec into one task per user story, declares real dependencies between them, and dispatches unblocked tasks in parallel to subagents with effort-based model tiers. Each task passes a review gate before completion, and progress is tracked in .sixth-sense/progress.md so work resumes correctly after interruptions.

When should I use the Light Workflow versus the Heavy Workflow?

Use the Light Workflow when the spec has 3 or fewer independent stories touching at most 2 files each — a single continuous TDD pass is faster. Use the Heavy Workflow for anything larger or requiring multi-file coordination, where per-task checkpoints prevent errors from propagating.

Does this workflow handle database schema or API migrations?

Yes, a dedicated migration reference covers schema, API, data, and dependency migrations. It requires mapping readers and writers, planning forward and rollback paths, and staging changes as expand, migrate, verify, contract with idempotent retries and explicit authorization for destructive steps.

What happens if a subagent task keeps failing review?

A circuit breaker tracks fix-review rounds per task: rounds 1-3 retry at the same tier, round 4 escalates one tier, and round 5 escalates to the highest tier. At that point the issue is adjudicated directly with a logged ruling rather than stopping to wait for the user.