update-notes
01Command Claude Code
Update CHANGENOTES.md and commit changes to prompts folder.
Kanban-style ticket board system using markdown files for storage. Features drag-and-drop ticket management, multi-project support, real-time updates, and integrated document viewer. Lightweight, version-control-friendly project management with MCP integration for AI assistants.
Command Claude Code
Update CHANGENOTES.md and commit changes to prompts folder.
Command
Surface architectural decisions before implementation. Output is minimal but complete.
Command
Assess affected code before architecture design. Surfaces the decision: integrate as-is, refactor inline, or split CRs.
Command
Generate BDD acceptance tests from requirements. Produce user-visible behavior tests that validate the system from the outside.
Command
Interactive clarification workflow for MDT architectural decision records (ADRs) using MCP mdt-all ticket system. Identifies underspecified areas in CR tickets and encodes answers directly into the ticket content.
Command
Analyze existing code for DDD violations AND structural issues. Output is a diagnostic report with severity and fix direction — not prescriptions.
Command
Surface strategic DDD constraints before architectural decisions. Output is intentionally minimal — principles only, not prescriptions.
Command
Execute with agent-based verification.
Command
Execute tasks from a task list with constraint verification after each task.
Command
Validate uncertain technical decisions through hands-on experimentation before committing to architecture.
Command
Capture post-implementation learnings from the conversation and selected workflow artifacts, then encode approved updates into the CR and any chosen MDT documents. Focus on artifact-level insights and specification adjustments only.
Command
Generate behavioral requirements from CR. Output: {TICKETSPATH}/{CR-KEY}/requirements.md.
Command
Suggest next MDT workflow based on ticket state.
Command
Generate tasks from architecture + tests + bdd. Tasks include constraints (scope boundaries, exclusions, anti-duplication), not just actions.
Command
On-demand detection of technical debt patterns in implemented code.
Command
Generate unit/integration tests from architecture design. Tests written AFTER architecture, BEFORE implementation.
Command
Pattern: Analyze context → Infer all parameters → Confirm/Refine → Execute.