DevCD

Capture continuity metadata on key execution triggers during work.

Close a session with a compact handoff before switching agents.

Recovery path when continuity packet readiness or tooling is limited.

Mandatory first move for local DevCD continuity before asking for recap.

Use when a change affects architecture, slice boundaries, API contracts, policy rules, or memory schemas. Creates or updates Architecture Decision Records (ADRs) before implementation. Keywords: ADR, decision record, proposed, architecture boundary, policy change, API contract, slice design.

Use when an agent ignores instructions, loses context, misuses tools, produces weak handoffs, behaves unreliably across multiple steps, or needs observability and operational guardrails. Covers instruction loading checks, handoff discipline, context compaction, multi-agent coordination, failure-mode analysis, and verification gates for agent-driven work.

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

Repository-safe commit and push workflow for DevCD. Use when preparing commits, choosing conventional commit messages, running validation, or deciding whether a push is allowed. Keywords: commit, push, git push, conventional commit, changelog, validation.

Installiert aus nexu-io/open-design: fuehrt eine evidenzbasierte 5-Dimensionen-Designkritik fuer Entwuerfe durch. Nuetzlich fuer Logo-Konzepte, Brandboards, Landing-Entwuerfe und visuelle Richtungen. Verwenden bei critique, design review, design audit, review my design, what's wrong with this.

"/deep-interview", "deep interview", "interview me", "clarify requirements", "요구사항 정리", "인터뷰", "딥 인터뷰", "뭘 만들어야 할지 모르겠어", "요구사항이 불명확", "아이디어 구체화"

Installiert aus nexu-io/open-design: strukturiert ein vages Marken- oder Logo-Briefing in eine konkrete Design-Spezifikation mit Palette, Typografie, Stimmung, Dichte und Constraints. Verwenden bei design brief, logo brief, brand brief, structured brief, ilang brief.

Use when a plan, feature, ADR, policy change, MCP surface, release step, or architectural direction needs aggressive stress-testing before implementation or rollout. This skill does not help build first; it finds weak assumptions, hidden blast radius, vague success criteria, and the fastest ways the idea could fail.

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".

Installiert aus nexu-io/open-design: erzeugt ein einzelnes Bildmotiv fuer Poster, Key Art oder visuelle Markenexploration. Nuetzlich fuer Logo-Moodboards, Symbolideen, Brand-Atmosphaere und visuelle Richtungen. Verwenden bei poster, key art, illustration, image, cover art, logo concept sheet.

Use when asked to audit, review, or improve the codebase architecture. MUST invoke for: architecture audit, codebase smell, coupling analysis, testability review, shallow module, deep module, slice coupling, module deepening, refactor RFC, AI-navigability, improve testability, what's wrong with the architecture, technical debt review, hard to test, too much coupling, module too large, spaghetti code.

Log learnings, errors, and corrections to .learnings/ for continuous improvement. Use when: (1) A command or operation fails unexpectedly, (2) User corrects the agent, (3) A knowledge gap is identified, (4) A better approach is found. Captures corrections, insights, errors, and feature requests; promotes broadly applicable learnings to project memory files.

Post-completion self-review for coding agents that runs simplify, harden, and micro-documentation passes on non-trivial code changes. Use when: a coding task just completed, the diff touches executable source files with 10+ changed lines or high-impact logic (auth, validation, queries, file paths, network, concurrency). Feeds recurring findings into self-improving-agent via .learnings/LEARNINGS.md.

Use when executing implementation plans with independent tasks in the current session. Dispatches fresh subagent per task with two-stage review (spec compliance, then code quality).

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes. Enforces 4-phase root cause investigation: no fixes without understanding the root cause first.

Use when implementing any feature or bugfix, before writing implementation code. Enforces RED-GREEN-REFACTOR cycle: write failing test first, watch it fail, write minimal code, watch it pass.

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always.

Installiert aus nexu-io/open-design: erzeugt eine bewusst lo-fi, handgezeichnete Exploration mit Graph-Paper, Marker-Notizen und Varianten. Fuer Logoarbeit eignet sich das als fruehes Konzeptblatt, Richtungsboard oder Symbol-Exploration vor dem Feinschliff. Verwenden bei wireframe, sketch wireframe, hand drawn, low fidelity, whiteboard sketch, concept sheet.

Use when you have a spec or requirements for a multi-step task, before touching code. Creates detailed, bite-sized implementation plans with exact file paths, complete code, and verification steps.

Start an OpenClaw coding session from DevCD's local Action Packet before asking the developer to recap.