isdd

Creates user-focused intent specifications in docs/<feature>/spec.md before implementation planning.

Updated Sep 7, 2026
One-click install
npx skills add https://github.com/deriye/.agents-work --skill isdd-deriye
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: isdd
Source: https://github.com/deriye/.agents-work/tree/main/skills/isdd
Command: npx skills add https://github.com/deriye/.agents-work --skill isdd-deriye

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often jump straight into coding without capturing what a feature should do from the user's perspective, leading to misaligned implementations and lost requirements. This Skill enforces an intent-first workflow by writing implementation-agnostic feature specs before any technical planning occurs. ## Core Features & Use Cases - Intent Spec Generation: Writes structured specs with Context, Desired Behavior, Boundaries, and Success Criteria sections, stored at docs/<feature>/spec.md. - Duplicate Detection: Scans existing docs/**/spec.md files and decides whether a request is a new feature or an update to an existing spec, using a detailed decision framework. - Implementation Gating: Stops after the spec is written and only produces an implementation plan (docs/<feature>/plan.md) when explicitly requested. - Use Case: A product manager says "users should be able to export their data as CSV." The Skill checks existing specs, creates docs/export-data-as-csv/spec.md describing the user experience, and waits before any technical planning. ## Quick Start Ask the assistant to create an intent spec for a new feature you want to add, describing it from the user's perspective.

Frequently Asked Questions about isdd

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

FAQPage Schema
How do I write a feature specification before coding?▼

Describe the feature from the user's perspective and let the Skill generate a spec at docs/<feature>/spec.md with Context, Desired Behavior, Boundaries, and Success Criteria sections. The spec contains no implementation details, libraries, or architecture decisions.

What is intent spec driven development?▼

Intent spec driven development is a workflow where every user-facing feature is first captured as an implementation-agnostic specification describing user goals and outcomes. Technical planning is gated until the spec exists and the user explicitly requests an implementation plan.

How do I decide if a request is a new feature or an update?▼

Compare the user goal, primary actor, and interaction pattern against existing specs. Same goal with a new method is an update; a different actor or distinct capability is a new feature. The feature-separation.md reference provides a decision table and examples.

When should I not use intent specifications?▼

Avoid intent specs for code reviews, refactoring, bug fixes without user-facing changes, and purely technical tasks like dependency migrations. The Skill only applies to capabilities that change what a user can do or experience.

Can a spec include technical implementation details?▼

No. Specs must remain implementation-agnostic, describing only user experience and outcomes. Technical plans are written separately at docs/<feature>/plan.md and only after the user explicitly requests implementation planning.