Agent Plugins Marketplace
← All plugins

tamheed

v4.10.0

Turn a project description into a validated, traceable, execution-ready planning & handoff package for Claude Code to implement.

Claude Code1 Skill1 MCP serverstdio

By Anas HammoLicense: MIT0 GitHub starsUpdated 2 days ago

Directory evidence

Runtimes
Claude Code
Parsed components
2 skill or MCP entries
Source updated
Sep 22, 2026
Manifest status
Canonical path parsed

The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →

Install tamheed for Claude Code

Installs for the current user
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install tamheed@agent-plugin-marketplace

Paste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.

The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.

Get the source manually
git clone https://github.com/A-H-911/tamheed

Clone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/tamheed/.

Plugin files

plugins/tamheed/
├── .claude-plugin/plugin.json
├── SKILL.md
└── .mcp.json

Included Skills1

tamheedSKILL.md

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.

MCP servers1

tamheedstdio
command
uv
args
run ${CLAUDE_PLUGIN_ROOT}/server/tamheed_server.py --package-dir ${CLAUDE_PROJECT_DIR}

MCP configuration uses runtime-provided plugin path placeholders such as ${PLUGIN_ROOT} or ${CLAUDE_PLUGIN_ROOT}. Review the manifest for the runtime-specific expansion rules.

Plugin manifests1

plugins/tamheed/.claude-plugin/plugin.json
{
  "name": "tamheed",
  "description": "Turn a project description into a validated, traceable, execution-ready planning & handoff package for Claude Code to implement.",
  "version": "4.10.0",
  "author": {
    "name": "Anas Hammo"
  },
  "homepage": "https://github.com/A-H-911/tamheed",
  "repository": "https://github.com/A-H-911/tamheed",
  "license": "MIT"
}

For maintainers

If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.

[tamheed on Agent Plugins Marketplace](https://pluginsmp.com/plugins/tamheed)