skills.rest
JamSuite
JamSuiteOFFICIAL
Explore all skills by this author →
GitHub

plan

Generate a coder-ready implementation plan from an approved spec.

1|1|Updated Feb 25, 2025
Search Tags:#architecture#documentation#spec#plan#task-breakdown#design-decisions
One-click install
npx skills add https://github.com/JamSuite/jim --skill plan-jamsuite
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/JamSuite/jim/tree/main/skills/plan
Command: npx skills add https://github.com/JamSuite/jim --skill plan-jamsuite

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

Produces a coder-ready implementation plan from an approved spec, ensuring a clear, auditable path from specification to concrete tasks and artifacts.

Core Features & Use Cases

  • Generates a complete plan.md from an approved spec, including design decisions, contracts, and a task breakdown.
  • Supports feature, bug, and refactor workflows with architecture constraints and research integration.
  • Use case: when a team receives a spec, run /jim:plan to produce a living plan that guides coding, testing, and release.

Quick Start

Provide the path to an approved spec.md and I will generate a coder-ready plan.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I turn an approved spec into a coder-ready implementation plan?▼

You can generate a coder-ready implementation plan by providing the path to an approved spec.md, which produces a comprehensive plan.md including design decisions, interface contracts, and a verifiable task breakdown.

What is included in a task breakdown for an architecture refactor?▼

A task breakdown for an architecture refactor includes a file manifest, interface contracts, data-flow diagrams, and verifiable tasks with explicit checks to ensure a clear, auditable path from specification to concrete artifacts.

Can I use this approach for both feature development and bug fixes?▼

Yes, you can use this approach for both feature development and bug fixes, as it supports feature, bug, and refactor workflows by applying architecture constraints and research integration to produce a living plan.

Do I need a frontmatter spec path to generate documentation?▼

Yes, you need a frontmatter spec path to generate documentation, because the process requires an approved spec.md path, type, and status to coordinate research and architecture constraints into a task-based plan.

Why does my implementation plan require interface contracts and data-flow diagrams?▼

Your implementation plan requires interface contracts and data-flow diagrams to establish a clear, auditable path from specification to concrete tasks, ensuring the generated plan is coder-ready and guides coding, testing, and release.

Related Skills

Explore More Software Engineering Skills→
blockblock
49

plan-conventions

Enforce frontmatter and lifecycle rules for plans under docs/plans/.

Official
Intermediate
JeremyDev87JeremyDev87
31

test-driven-development

Enforce a Red-Green-Refactor cycle with failing tests before implementation.

Community
Advanced
telum-aitelum-ai
2

project-architecture

Design system architecture blueprints for greenfield and brownfield projects.

Official
Advanced
sddevelopment-besddevelopment-be
13

File-Based Asynchronous Agent Orchestration (Superseded)

Coordinate asynchronous agent workflows via file-based signaling triggers.

Official
Basic