tamheedlisted

Transform a project description into a complete, validated, traceable, execution-ready planning and handoff package for Claude Code to implement — requirements, constraints, invariants, assumptions, open decisions, risks, architecture + ADRs, technology comparisons, R&D/experiment plans, a phased roadmap with slices, acceptance criteria, full traceability, and handoff prompts — stored as a relational package (SQLite runtime, canonical JSONL) written only through the Tamheed MCP tools. Use whenever the user wants to plan, scope, spec, or "inception" a project; run an R&D, architecture, or design mission; produce a charter or execution plan; de-risk a build before coding; update a package as execution progresses; or prepare kickoff prompts for Claude Code. Trigger on "plan this project", "turn this idea into a plan", "scope this out", "design before we build", "prepare a handoff", "project charter", or a long pasted project brief — even if the word "Tamheed" is never said.
A-H-911/tamheed · ★ 0 · AI & Automation · score 72

Install: claude install-skill A-H-911/tamheed

# Tamheed Tamheed turns a project description into an **execution-ready handoff package**: the planning, research, architecture, governance, and execution artifacts Claude Code needs to implement the project with discipline. It is the successor of Keystone: the same 22-stage methodology, now backed by a **relational package store** (ADR-0001) instead of loose Markdown files. **Requirements.** An MCP-capable host (Claude Code loads the bundled server via `.mcp.json` automatically). The server needs **Python ≥3.10** and the official `mcp` SDK — `uv` runs it with zero setup (PEP 723), or `pip install mcp` as the fallback. See `server/README.md`. **One principle governs the whole design: the skill owns the capability.** Every entry point is a thin wrapper that normalizes input and routes output; none re-implements the methodology. The MCP server is **not** an entry point — it is the mechanical half of the capability itself (the successor of the v1 validator): the only write path into a package, where the referential quality gates are schema constraints that cannot be skipped. ## What Tamheed produces A relational package (layout: `references/generated-structure.md`) containing, as applicable: **register entities** — functional/non-functional requirements, constraints, invariants, assumptions, dependencies, open questions, decisions, ADRs, risks (with execution lifecycle), hypotheses, experiments, POCs, tests, KPIs, stakeholders, phases → **slices**, work items, milestones, a