domain driven design commands

dogganidhal/noddde

Command Claude Code

Show the implementation status of all specs in the project, following .claude/skills/spec-status/SKILL.md exactly.

dogganidhal/noddde

Command Claude Code

Spec-driven development orchestrator. Drive the full 6-step pipeline for the requested change, following .claude/skills/spec/SKILL.md exactly.

bardiakhosravi/tenets

Command

You are a strict architecture reviewer for a codebase following Hexagonal Architecture (Ports & Adapters) with Domain-Driven Design.

bardiakhosravi/tenets

Command

You are initializing the architecture foundation for the Flask service in the current repository. This workflow supports one service only. It does not generate individual bounded contexts, workflows, features, or resources.

jed1978/ddd-architecture-coach

Command

Launch the DDD Architecture Coach. With no argument, shows an in-flight summary derived from {coachoutputroot}/ and asks which BC to focus on. With a BC name, derives the next phase for that BC and enters it. Use this as the default entry point.

jed1978/ddd-architecture-coach

Command

Force entry into Phase 1 (Domain Discovery). Skips state-based phase selection. Use when you explicitly want to (re-)run scenario modeling, event/command extraction, BC delineation, classification, touchpoint map, AI opportunities, or User Stories. With no argument → system-level Steps 1–5. With a BC name → per-BC…

jed1978/ddd-architecture-coach

Command

Force entry into Phase 2 (Architecture Design) for one BC. Requires explicit BC argument. Use when you want to (re-)work on Context Map, per-BC architecture decisions, cloud deployment, or AI-ADRs for a specific BC.

lugassawan/swe-workbench

Command

Run an unattended review→fix→re-review loop on the current branch until the reviewer has no findings at or above Medium, then push once. Findings stay in a local scratch file and are never posted to GitHub. Stops early on oscillation, a red test suite, or a 4-review cap.

lugassawan/swe-workbench

Command

Diagnose a bug, failing test, or unexpected behavior — root-cause first, minimal fix, regression test. Performance-shaped symptoms (slow, latency, profiling) are routed to workflow-performance-investigation via one clarifying question.

lugassawan/swe-workbench

Command

Review the current git diff — auditor selected by --mode (general, security, a11y, deps, perf, tests, contributor-trust, ux) or auto-inferred from the diff when omitted. Pass a PR number to review a specific PR; use --check-followup to re-check a PR after the owner has addressed feedback.