agentic-dev-workflow

A Claude Code plugin marketplace hosting four plugins, each under plugins/<name>/:

• agentic-dev-workflow — a modular, tool-agnostic dev-workflow harness: planning, PR readiness, testing, and CI-failure investigation skills that name capabilities (tracker, code_host, ci, quality) and resolve them to concrete tools via a per-repo config. It also models a repo's stack as modules — each bound to an ecosystem adapter (dotnet/angular/terraform/…) that carries its lint/format/test/analyze/LSP tooling — and runs per-module local gates before a PR.
• architecture — system/service-level architecture design (arch-design) and adversarial design review (arch-review). Tool-agnostic, no config. See plugins/architecture/README.md.
• csharp-ddd-fp — an enforceable C# DDD + functional-programming rule set: a handbook, a copy-in analyzer/arch-test pack, and skills to author/review/adopt the conventions. See plugins/csharp-ddd-fp/README.md.
• zettelkasten-vault — a Zettelkasten / daily-note vault workflow: fast capture, inbox distillation into linked zettels, daily planning with read-only work context, weekly review, and Syncthing conflict reconciliation. Enforced vault structure (notes/{open,done,reference}/, month-foldered dailies and journals). See plugins/zettelkasten-vault/README.md.

Install (Claude Code)

All four plugins are served from this one Codeberg repo. Add it as a marketplace once, then install whichever plugins you want.

1. Add this repo as a plugin marketplace:

   /plugin marketplace add https://codeberg.org/anton_bauer/agentic-dev-workflow.git
   

2. Install the plugin(s) you want (all share the @agentic-dev-workflow marketplace suffix):

   /plugin install agentic-dev-workflow@agentic-dev-workflow
   /plugin install architecture@agentic-dev-workflow
   /plugin install csharp-ddd-fp@agentic-dev-workflow
   /plugin install zettelkasten-vault@agentic-dev-workflow
   

3. For the dev-workflow harness, run the guided setup once in each repo you want to use it in:

   /dev-workflow-init
   

   This sniffs the repo's tooling and writes .claude/dev-workflow.config.yaml (schema: docs/configuration.md), which selects one adapter per capability and records your project constants.

Dependencies

This harness builds on other plugins and skills. See docs/dependencies.md for the full list.

Required plugins (auto-installed via the plugin's dependencies once both marketplaces have been added; until then, or if either is missing, the harness is disabled with a dependency-unsatisfied error):

/plugin marketplace add obra/superpowers-marketplace
/plugin marketplace add JuliusBrussee/caveman

• superpowers — the planning/TDD/review skills the harness orchestrates. Also on anthropics/claude-plugins-official.
• caveman — agent-output compression; auto-activates once installed.

Required skills (Matt Pocock family — not a plugin): grilling, domain-modeling, tdd. Install user-wide, Claude Code only, via the official skills CLI (exact commands in plugins/agentic-dev-workflow/docs/dependencies.md): npx skills@latest add mattpocock/skills --skill grilling -g -a claude-code -y --copy (repeat per skill). The harness warns at session start (in repos it's configured for) and at /dev-workflow-init if any are missing.

Optional: rtk (Rust Token Killer) — install for extra token savings; the harness detects it and runs unchanged when it's absent. session-eval (ai-harness-eval) — install for per-session quality scorecards; likewise soft-detected and non-blocking when absent.

Updating and versioning

Each plugin carries its own semver in its plugins/<name>/.claude-plugin/plugin.json — the four release lines are independent, because you install them independently. Claude Code pins an installed plugin to that version string, so /plugin update delivers changes only when the field is bumped (not on every push to main).

Current: agentic-dev-workflow 0.1.0 · architecture 0.2.0 · csharp-ddd-fp 0.1.0 · zettelkasten-vault 0.2.0. Per-plugin history in plugins/<name>/CHANGELOG.md.

All four are pre-1.0, so a MINOR bump can carry a breaking change; those are marked ### BREAKING with migration steps in the changelog. Read the changelog before taking an update to a plugin whose conventions your repo or vault already follows.

Contributing: the bump-and-changelog rule is enforced by a git hook, opted into once per clone with git config core.hooksPath .githooks. Full strategy in VERSIONING.md.

Extending

• Add a tool behind an existing capability: docs/writing-an-adapter.md.
• Add support for a new language/toolchain: author an ecosystem adapter — see the "Authoring an ecosystem adapter" section of docs/writing-an-adapter.md.
• Config schema and module menu: docs/configuration.md.
• Start from a shipped profile: a profile under plugins/agentic-dev-workflow/profiles/<name>/ is a bundle — config.yaml plus an optional dev-workflow/{adapters,checks,policies,hooks}/ tree that mirrors your repo's .claude/dev-workflow/ root. plugins/agentic-dev-workflow/profiles/github-example/ stays minimal (config-only, single-repo GitHub + GitHub Actions); plugins/agentic-dev-workflow/profiles/submodules-example/ is the fuller worked example (ADO + Jira + submodules, with a repo-local ecosystem override, a per-module override, and an extra PR-readiness check + policy docs). Adopting one is a two-copy step: copy config.yaml → .claude/dev-workflow.config.yaml, then copy the dev-workflow/ tree (if present) → .claude/dev-workflow/. /dev-workflow-init offers to do both automatically when your sniffed repo matches a profile's shape.

Repository note

Canonical remote is Codeberg. gh CLI does not apply here; use plain git.