Menu
Route and record architectural and technical decisions for SoloDevBoard using the repo memory model (constitution, decision log, feature issues).
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Diátaxis Documentation Expert. Creates high-quality software documentation using the Diátaxis framework.
Orchestrates end-to-end feature delivery for SoloDevBoard: planning, GitHub issue management, implementation gating, testing, documentation, and closure.
Guide for using the MudBlazor component library in Blazor Server applications. Use this when building or refactoring Blazor pages and components for SoloDevBoard. Covers setup, layout, component usage patterns, dialog and snackbar services, data grids, forms, colour pickers, theming, and bUnit testing with MudBlazor. Also use when troubleshooting z-index, popup rendering, or styling issues.
Manage the SoloDevBoard Roadmap GitHub Project (Project #8). Add issues to the board, set Phase/Priority/Status/Date fields, manage the Up Next queue, and keep the project in sync with the issue lifecycle. Use this skill whenever creating or updating GitHub issues for SoloDevBoard.
Create, update, and manage GitHub issues using MCP tools. Use this skill when users want to create bug reports, feature requests, or task issues, update existing issues, add labels/assignees/milestones, or manage issue workflows. Triggers on requests like "create an issue", "file a bug", "request a feature", "update issue X", or any GitHub issue management task.
Get best practices for XUnit unit testing, including data-driven tests
| name | repo-decision-log |
| description | Route and record architectural and technical decisions for SoloDevBoard using the repo memory model (constitution, decision log, feature issues). |
Use this skill when a change introduces or changes a technical or architectural decision. Do not create new ADR files in adr/.
| Situation | Where to record | Example |
|---|---|---|
| Permanent cross-cutting rule every agent must follow | Constitution — AGENTS.md and/or .github/instructions/ | DTO boundary, banned libraries, deploy model |
| Significant decision not fully captured in constitution | Decision log — plan/DECISIONS.md | API strategy, auth phasing, migration scope |
| Feature-scoped choice | GitHub issue + wireframe or plan note | Preview UX, single-endpoint behaviour |
| Historical full prose | Do not add — adr/archive/ is read-only | — |
When in doubt: promote to constitution only if violating the rule would break builds, security, or layer boundaries on every future change.
Append to plan/DECISIONS.md under Active decisions:
### DEC-NNN: Short title
**Status:** Active
**Date:** YYYY-MM-DD
**Legacy:** _(omit for new decisions; link ADR archive only when migrating)_
**Constitution:** _(link if also reflected in AGENTS.md or instructions)_
**Summary:** One paragraph — rule, rationale, what to reject.
Increment DEC-NNN from the highest existing number. Mark superseded entries Status: Superseded and add a row to the Superseded legacy table if replacing an older DEC.
When updating constitution:
AGENTS.md and/or the relevant .github/instructions/*.md file.plan/DECISIONS.md with a Constitution link.plan/DOCS_STRATEGY.md only if documentation process changes.adr/ or adr/archive/.DECISIONS.md holds summaries.When plan/SPEC_KIT_MIGRATION.md is executed, feature decisions will move into Spec Kit specs and constitution. Until then, follow this skill.