By alexnodeland
Orchestrate DDD plan execution via worktree-isolated Claude Code agents. Decomposes plans into tasks, spawns agents in git worktrees, validates implementations, and merges results.
Validate task implementations by running the project's test suite, linters, and CI checks. Discovers test commands from common project patterns (package.json, Makefile, pytest, cargo, go) and reports pass/fail with details. Use after a sub-agent completes a task.
Decompose a DDD plan into executable tasks with dependency ordering. Reads a plan file, extracts phases, bounded contexts, and individual tasks, then creates a task manifest for orchestration. Use when you have an active DDD plan ready for implementation.
Implementation orchestration strategy for the Principled framework. Consult when working with DDD plan execution, git worktrees for task isolation, task manifests, or the decompose-spawn-validate-merge lifecycle. Covers worktree management, sub-agent patterns, task state machines, and manifest schema.
Merge a completed and validated task's worktree branch back to the working branch. Verifies checks passed, performs the merge, cleans up the worktree, and updates the task manifest. Directly invocable by users and by the orchestrate skill.
Top-level orchestrator for DDD plan execution. Decomposes a plan into tasks, iterates through phases respecting dependencies, spawns worktree-isolated agents, validates implementations, and merges results. Runs inline to coordinate multiple sub-agent spawns. Use for automated end-to-end plan execution.
Modifies files
Hook triggers on file write and edit operations
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
📐 Principled Marketplace
A curated Claude Code plugin marketplace for specification-first development.
A Claude Code plugin marketplace hosting first-party and community plugins for the Principled specification-first methodology. Add the marketplace once, install any plugin.
| Plugin | Category | Description |
|---|---|---|
| principled-docs | documentation | Scaffold, author, and enforce module documentation structure following the Principled specification-first methodology (v0.3.1) |
| principled-implementation | implementation | Orchestrate DDD plan execution via worktree-isolated Claude Code agents (v0.1.0) |
| principled-github | workflow | Integrate the principled workflow with GitHub native features: issues, PRs, templates, actions, CODEOWNERS, and labels (v0.1.0) |
| principled-quality | quality | Connect code reviews to the principled documentation pipeline with spec-driven checklists and review tracking (v0.1.0) |
| principled-release | workflow | Generate changelogs from the documentation pipeline, verify release readiness, and coordinate versioned releases (v0.1.0) |
| principled-architecture | architecture | Map modules to governing ADRs, detect architectural drift, audit governance coverage, and sync architecture docs (v0.1.0) |
No community plugins yet. See Contributing to submit one.
/plugin marketplace add alexnodeland/principled
/plugin install principled-docs@principled-marketplace
/plugin install principled-implementation@principled-marketplace
/plugin install principled-github@principled-marketplace
/plugin install principled-quality@principled-marketplace
/plugin install principled-release@principled-marketplace
/plugin install principled-architecture@principled-marketplace
Add to your project's .claude/settings.json:
{
"extraKnownMarketplaces": {
"principled-marketplace": {
"source": {
"source": "github",
"repo": "alexnodeland/principled"
}
}
},
"enabledPlugins": {
"principled-docs@principled-marketplace": true,
"principled-implementation@principled-marketplace": true,
"principled-github@principled-marketplace": true,
"principled-quality@principled-marketplace": true,
"principled-release@principled-marketplace": true,
"principled-architecture@principled-marketplace": true
}
}
principled/
├── .claude-plugin/
│ └── marketplace.json # Plugin catalog
├── plugins/ # First-party plugins
│ ├── principled-docs/ # Documentation structure plugin
│ ├── principled-implementation/ # Plan execution plugin
│ ├── principled-github/ # GitHub integration plugin
│ ├── principled-quality/ # Code review quality plugin
│ ├── principled-release/ # Release lifecycle plugin
│ └── principled-architecture/ # Architecture governance plugin
├── external_plugins/ # Community plugins
├── docs/ # Marketplace governance
│ ├── proposals/ # RFCs
│ ├── plans/ # Implementation plans
│ ├── decisions/ # ADRs
│ └── architecture/ # Design docs
└── .claude/ # Dev configuration
First-party plugins live in plugins/. They are maintained by the project and must:
npx claudepluginhub alexnodeland/principled --plugin principled-implementationScaffold, author, and enforce module documentation structure following the Principled specification-first methodology.
Connect code reviews to the principled documentation pipeline with spec-driven checklists, context surfacing, coverage assessment, and structured review summaries.
Generate changelogs from the documentation pipeline, verify release readiness, coordinate version bumps, and govern the release lifecycle.
Map code to architectural decisions, detect drift, audit decision coverage, and keep architecture documents synchronized with the codebase.
Integrate the Principled specification-first workflow with GitHub native features: issues, pull requests, templates, actions, CODEOWNERS, and labels.
'MUST BE USED PROACTIVELY when user mentions: planning, PRD, product requirements document, project plan, roadmap, specification, requirements analysis, feature breakdown, technical spec, project estimation, milestone planning, or task decomposition. Use IMMEDIATELY when user says "create a PRD", "plan this feature", "document requirements", "break down this project", "estimate this work", "create a roadmap", "write specifications", or references planning/documentation needs. Expert Technical Project Manager that creates comprehensive PRDs with user stories, acceptance criteria, technical architecture, task breakdowns, and separate task assignment files for sub-agent delegation.'
Blueprint Development methodology - structured feature development with PRD/PRP workflow, three-layer architecture (plugin/generated/custom), and documentation-first development
Implementation planning, execution, and PR creation workflows with multi-agent collaboration
Comprehensive skills library for Claude Code: planning, design, TDD, debugging, collaboration patterns, and proven techniques
Context-Driven Development plugin that transforms Claude Code into a project management tool with structured workflow: Context → Spec & Plan → Implement
Git and PR workflows with code review, onboarding, and PR enhancement