specimin-plan

Generate high-level implementation plans from feature specifications using Tree-of-Thought exploration.

Updated Nov 7, 2025

Search Tags:#planning #architecture #spec #tree-of-thought #design decisions

Ready to run

npx skills add https://github.com/timsvoice/specimin --skill specimin-plan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: specimin-plan
Source: https://github.com/timsvoice/specimin/tree/main/.claude-plugin/skills/specimin-plan
Command: npx skills add https://github.com/timsvoice/specimin --skill specimin-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, and includes scripts (resource) components.

What problem does it solve?

Helps architects craft high-level implementation plans using structured reasoning to explore options and justify decisions.

Core Features & Use Cases

Tree-of-Thought exploration: evaluate multiple approaches and select the best plan.
Component mapping: outline plan components, dependencies, and interfaces.
Rationale docs: explain why each choice was made.

Quick Start

After specification, run the planning tool to generate a plan draft for your branch.

Frequently Asked Questions about specimin-plan

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

FAQPage Schema

How do I create a high-level implementation plan from a feature specification?▼

Generate a high-level implementation plan by running the planning tool on your feature specification. The tool uses Tree-of-Thought exploration to evaluate multiple approaches, asks clarifying questions, and produces a structured plan.md file that outlines components, dependencies, and design rationale without implementation details.

What is Tree-of-Thought exploration in architecture planning?▼

Tree-of-Thought exploration is a structured reasoning technique that evaluates multiple solution approaches systematically, weighs trade-offs, and justifies the selected design path. It helps architects make informed decisions by mapping alternative routes before committing to a plan.

Do I need an existing specification before generating a plan?▼

Yes, an existing spec.md file in your .specimin/plans/{branch}/ directory is required. The planning tool analyzes your codebase and specification together, then asks clarifying questions to produce a tailored implementation plan.

How does the planning tool integrate with my workflow?▼

The planning tool outputs plan.md to your feature directory and integrates with save-plan.sh for committing changes to git. This Stage-based workflow keeps your planning artifacts versioned alongside your specification and code.

What should I do after generating a plan?▼

Review the generated plan.md, which includes component mappings, dependencies, interfaces, and design rationale. Use save-plan.sh to commit the plan to your branch, then proceed to implementation aligned with the documented architecture decisions.