Repository navigation
feat(framework): specialized plugins — craftsmanship and tech stacks #148
Description
Problem
The framework has no plugin for engineering craft (clean code, refactoring, design patterns), and no way to ship rules for a specific tech stack. Stack-specific guidance has nowhere to live.
Scope
- A craftsmanship plugin: clean code, refactoring catalogue, design patterns.
- One plugin per stack: TypeScript/React, Python, and so on. A stack's rules become plugin content, not a folder of rules.
- A documented convention so a third party can author a stack plugin.
Acceptance criteria
- The craftsmanship plugin is published in the marketplace.
- The stack-plugin convention is documented well enough for someone outside the team to follow it.
Blocked by
Plugin Author DX, tracked in the ai-driven-dev/aidd-cli repository. Nothing here can ship until a third party can author and publish a plugin. That dependency is not visible from this board.
Origin
Backlog audit 2026-05-21. Replaces the old #53, whose premise (a monolithic rules/02-07/ tree) is dead.
Activity
[-]feat: plugins spécialisés (craftsmanship + stacks techno)[/-][+]feat(framework): specialized plugins — craftsmanship and tech stacks[/+]blafourcade commentedon Sep 8, 2026
Clôturée comme obsolète :
aidd-devcouvre désormais audit de qualité, clean code et refactoring ;aidd plugin create,aidd-context:05-rule-generateetdocs/CREATE_PLUGIN.mdfournissent le socle de création, règles et publication de plugins. Un plugin de stack ne sera créé que pour un besoin et une audience explicitement établis.