By alexnodeland
Integrate the Principled specification-first workflow with GitHub native features: issues, pull requests, templates, actions, CODEOWNERS, and labels.
Generate or update a CODEOWNERS file from the repository's module structure and git history. Maps module boundaries to code ownership using principled documentation structure as the guide. Use when setting up or refreshing code ownership rules.
Scaffold GitHub-specific configuration files aligned with the principled workflow. Creates issue templates, PR templates, actions workflows, and config files in the .github/ directory. Use when setting up a new repo or adding principled GitHub integration to an existing one.
GitHub integration strategy for the Principled framework. Consult when working with GitHub issues, pull requests, labels, CODEOWNERS, or .github/ templates in the context of the principled documentation pipeline. Covers issue-proposal mapping, PR-plan alignment, label taxonomy, and the GitHub-principled sync model.
Ingest a GitHub issue into the principled pipeline. Fetches the issue, determines what documents are needed (proposal, plan, or both), creates them pre-populated from issue content, and comments on the issue with links to the new documents on a feature branch.
Validate that a pull request follows principled conventions: references a plan or proposal, has correct labels, includes required sections in the description, and links to relevant documents. Use in CI or before merging to enforce PR quality.
Executes bash commands
Hook triggers when Bash tool is used
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-githubScaffold, 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.
Orchestrate DDD plan execution via worktree-isolated Claude Code agents. Decomposes plans into tasks, spawns agents in git worktrees, validates implementations, and merges results.
Map code to architectural decisions, detect drift, audit decision coverage, and keep architecture documents synchronized with the codebase.
GitHub project operations with quality gates.
Git and PR workflows with code review, onboarding, and PR enhancement
Provides comprehensive PR creation guidance with GitHub CLI, enforcing title conventions, following template structure, and offering concrete command examples with best practices.
Git workflows - commits, branches, PRs, issue processing, auto-close detection, and repository management
Provides comprehensive PR creation guidance with GitHub CLI, enforcing title conventions, following template structure, and offering concrete command examples with best practices.
Harness-native ECC operator layer - 67 agents, 271 skills, 92 legacy command shims, reusable hooks, rules, selective install profiles, and production-ready workflows for Claude Code, Codex, OpenCode, Cursor, and related agent harnesses