jds-plan

Translate confirmed specs into executable implementation plans with TDD tasks.

13|Updated Mar 24, 2026

Search Tags:#automation #workflow #planning #tdd #execution #spec #plan

Ready to run

npx skills add https://github.com/josipmusa/jds --skill jds-plan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: jds-plan
Source: https://github.com/josipmusa/jds/tree/main/skills/jds-plan
Command: npx skills add https://github.com/josipmusa/jds --skill jds-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning and translating a confirmed spec into an executable, verifiable implementation plan that ensures atomic tasks and no placeholders, enabling reliable delivery of software plans.

Core Features & Use Cases

Converts a confirmed spec into an actionable plan with 2-5 minute tasks, complete file maps, and verification steps
Supports both spec-driven planning (docs/jds/specs/) and moderated tasks where the spec is skipped
Enforces a TDD-first workflow and maintains a strict no-placeholder rule across all tasks

Quick Start

Create the plan by mapping file changes, composing 2-5 minute tasks with concrete verification steps, and store the result in docs/jds/plans/YYYY-MM-DD-<feature-name>.md.

Frequently Asked Questions about jds-plan

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

FAQPage Schema

How do I turn a software spec into an executable implementation plan?▼

To turn a software spec into an executable implementation plan, you map confirmed specifications into atomic 2-5 minute tasks with exact file paths, complete code, TDD structure, and SQL-based tracking. This process ensures verifiable delivery without placeholders.

What is an atomic verifiable task in TDD workflow planning?▼

An atomic verifiable task in TDD workflow planning is a 2-5 minute implementation unit containing exact file paths, complete code, and concrete verification commands. It enforces a strict no-placeholder rule to ensure reliable software delivery.

Can I generate an implementation plan for moderate tasks without a spec?▼

Yes, you can generate an implementation plan for moderate tasks without a spec. The planning workflow applies directly to moderate tasks where the spec phase was skipped, enforcing file maps and TDD structure without requiring docs/jds/specs/.

How to structure implementation plans using SQL-based task tracking?▼

To structure implementation plans using SQL-based task tracking, you break confirmed specs into 2-5 minute tasks mapped to exact file paths, embed verification commands, and store the output in docs/jds/plans/YYYY-MM-DD-<feature-name>.md without including commit steps.

Why does my implementation plan still contain placeholders?▼

Implementation plans contain placeholders when the planning workflow does not enforce a strict no-placeholder rule. Translating a confirmed spec must require exact file paths and complete code for every 2-5 minute atomic task to eliminate placeholders entirely.