ido4specs
Bogdan Coman v0.4.3
ido4specs is the bridge between a strategic spec and GitHub issues. It analyzes your codebase, decomposes capabilities into implementation tasks with effort, risk, type, and dependency metadata, an...
From the developer
License
MIT
Works with
Claude Code
Description
From the marketplace listing
ido4specs is the bridge between a strategic spec and GitHub issues. It analyzes your codebase, decomposes capabilities into implementation tasks with effort, risk, type, and dependency metadata, and produces a structurally-validated technical spec any downstream tool can consume. Key features: - Code-grounded decomposition - parallel Explore subagents ground every task in concrete files, services, and patterns from your actual codebase (not fabricated from the spec) - Structured output enforced by a bundled zero-dependency parser - every task carries effort (S/M/L/XL), risk (low → critical), type (feature/infrastructure), AI-suitability (full/assisted/pair/human), and dependency graph - Two-layer validation - deterministic structural parser + independent qualitative review before handoff Built for tech leads, staff engineers, and founder-engineers who want to skip the manual decomposition tax.
What changed
No changes recorded yet. Follow this plugin to keep track of future changes.
Similar plugins
Find competitors to follow as you develop your plugin.
-
Get up to speed in any codebase, any size. Non-opinionated workflow plugin with session journaling, local task tracking, GitHub issue syn...
Shared terms: codebase, github, issue, task
-
Comprendo gates AI implementation behind a visual developer approval step. When you type /comprendo <task>, Claude reads your codebase, b...
Shared terms: codebase, implementation, type, task
-
Spec-driven development workflow - transforms ideas into structured specifications (requirements, design, tasks) before implementation.
Shared terms: implementation, spec, task, structured
-
Effort estimation for AI coding agents. PERT three-point estimation with METR reliability thresholds, modifier stacks (spec clarity, warm...
Shared terms: effort, spec, github, issue
-
Spec-driven development framework for Claude Code. Manages the propose → plan → build → verify → pr lifecycle with structured proposals, ...
Shared terms: github, spec, task, structured
Keywords
Files & skills
ido4specs · catalog manifest
Saved declaration
{}
ido4specs · catalog manifest
Saved declaration
{
"name": "ido4specs",
"source": {
"sha": "3b230e874a8b26ee0558d800fe5cb8b76821a730",
"url": "https://github.com/ido4-dev/ido4specs.git",
"source": "url"
},
"homepage": "https://ido4.dev/specs",
"description": "ido4specs is the bridge between a strategic spec and GitHub issues. It analyzes your codebase, decomposes capabilities into implementation tasks with effort, risk, type, and dependency metadata, and produces a structurally-validated technical spec any downstream tool can consume.\n\nKey features:\n- Code-grounded decomposition - parallel Explore subagents ground every task in concrete files, services, and patterns from your actual codebase (not fabricated from the spec)\n- Structured output enforced by a bundled zero-dependency parser - every task carries effort (S/M/L/XL), risk (low → critical), type (feature/infrastructure), AI-suitability (full/assisted/pair/human), and dependency graph\n- Two-layer validation - deterministic structural parser + independent qualitative review before handoff\n\nBuilt for tech leads, staff engineers, and founder-engineers who want to skip the manual decomposition tax."
}
ido4specs · catalog manifest
Saved declaration
{
"name": "ido4specs",
"author": {
"url": "https://github.com/ido4-dev",
"name": "Bogdan Coman",
"email": "coman2904@gmail.com"
},
"license": "MIT",
"version": "0.4.3",
"homepage": "https://github.com/ido4-dev/ido4specs",
"keywords": [
"technical-spec",
"task-decomposition",
"implementation-planning",
"engineering-planning",
"code-analysis",
"github-issues",
"claude-code",
"ido4"
],
"repository": "https://github.com/ido4-dev/ido4specs",
"description": "The bridge between a strategic spec and GitHub issues. Analyzes your codebase, decomposes capabilities into implementation tasks with effort, risk, and dependency metadata, and produces a methodology-neutral technical spec any planning tool can consume. For tech leads and staff engineers who want to skip the manual decomposition tax."
}
plugin.json observed Nov 6, 2026 · 10:45 UTC. Manifest source ↗
Catalog declarations and available plugin.json metadata are saved. Referenced skills and executable source files are not downloaded or tested. Missing components in a manifest do not prove that the plugin has none.
Installation instructions
Community
/plugin marketplace add anthropics/claude-plugins-community
/plugin install ido4specs@claude-community
Technical details
- Sources
- Community
- First seen
- Oct 3, 2026 · 22:13 UTC
- Last seen
- Nov 7, 2026 · 12:00 UTC
- Latest observed change
- Oct 3, 2026 · 22:13 UTC
- Collection status
- Listed
- Reported installs
- Not provided
Installation counts are source-reported, not independently verified active users. Observation dates are not release dates.
Download plugin data (JSON)Plugin history: freshly prepared. Prepared . Refreshed when catalog data changes or after 6 hours. Your account and Follow status are live.