Structured ADR creation in MADR format. Triggers: ADR, Architecture Decision, 決定記録, 技術選定, アーキテクチャ決定, design decision, 技術的決定, 設計判断, deprecation, 非推奨化, process change, プロセス変更
/plugin marketplace add thkt/claude-config/plugin install complete-workflow-system@thkt-development-workflowsThis skill is limited to using the following tools:
EVALUATIONS.mdREADME.mdassets/architecture-pattern.mdassets/deprecation.mdassets/process-change.mdassets/technology-selection.mdreferences/impact-analysis.mdreferences/rollback-plan.mdreferences/test-coverage.mdscripts/pre-check.shscripts/update-index.shscripts/validate-adr.shCreate Architecture Decision Records in MADR format through a structured 6-phase process.
| Phase | Purpose | Key Actions |
|---|---|---|
| 1. Pre-Check | Prevent duplicates | Check existing ADRs, validate naming, verify directory |
| 2. Template | Select structure | Choose from 4 templates based on decision type |
| 3. References | Gather evidence | Collect project docs, issues, PRs, external resources |
| 4. Validate | Quality assurance | Verify required sections, check completeness |
| 5. Index | Update documentation | Auto-generate ADR list, cross-link related ADRs |
| 6. Recovery | Handle errors | Auto-fix paths, fallback templates |
| Template | Use Case | Required Sections |
|---|---|---|
| technology-selection | Library, framework choices | Options (min 3), Pros/Cons |
| architecture-pattern | Structure, design policy | Context, Consequences |
| process-change | Workflow, rule changes | Before/After comparison |
| deprecation | Retiring technology | Migration plan, Timeline |
| Phase | Key Actions |
|---|---|
| 1. Pre-Check | ls docs/adr/*.md, check duplicates, get next number |
| 2. Template | Match keywords to template type |
| 3. References | Gather project docs, issues, external resources |
| 4. Validate | Check required sections (Title, Status, Context, Decision, Consequences) |
| 5. Index | Auto-generate docs/adr/README.md |
| 6. Recovery | Handle missing dirs, duplicates, missing sections |
| Aspect | /rulify | /adr:skill |
|---|---|---|
| Purpose | Enforce constraints | Suggest patterns |
| Application | Always active | Triggered by keywords |
| Output | docs/rules/ | .claude/skills/ |
Use rule for: Security requirements, absolute constraints Use skill for: Implementation patterns, context-dependent guidance
| Practice | Do | Don't |
|---|---|---|
| Triggers | Specific terms: "React Query", "useQuery" | Generic: "code", "implement" |
| Examples | Project-specific code | Generic samples |
| Checklist | Actionable items | Vague guidance |
| Updates | Regenerate when ADR changes | Keep stale skills |
docs/adr/
├── README.md # Auto-generated index
├── 0001-*.md # Sequential numbering
└── 0002-*.md
.claude/skills/
├── adr-0001-*/ # Generated skills
│ └── SKILL.md
└── adr-0002-*/
└── SKILL.md
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.