digital-innovation-agents

Creates and manages unit tests and integration tests. Analyzes the existing codebase, auto-detects the test framework, and generates tests that follow project conventions. Use this skill when the user mentions "write tests", "unit tests", "integration tests", "test coverage", "testing", "tests missing", "TDD" or similar. Also after implementation when tests need to be created or updated.

Performs a COMPREHENSIVE, formal security audit of an entire codebase and produces a written audit report (AUDIT-{PROJECT}-{DATE}.md) with prioritized findings (H/M/L) and a remediation plan. Covers SAST, OWASP Top 10, OWASP LLM Top 10, SCA (dependency analysis), Zero Trust validation, code quality. Takes 30+ minutes. TRIGGER ONLY when the user explicitly requests a formal full-codebase audit producing a report: "security audit", "OWASP audit", "full security review", "AUDIT-Report erstellen", "Codebase auditieren", "SCA audit", "dependency audit", "CVE audit", "Sicherheitsaudit". DO NOT trigger for: PR-level security checks (use the built-in security-review skill), one-off security questions, threat-modeling discussions without an audit report, individual finding fixes, or generic mentions of "secure" / "security".

Brownfield entry point for the V-Model workflow. Reverse-engineers an existing codebase into the standard V-Model artifacts: plan-context.md, ADRs, arc42 snapshot, FEATURE inventory, backlog seed, and an evidence-based BA draft. Walks the V backwards from Coding up to Business Analysis, filling every step only with what can be proven from the code or the existing documentation. Every claim is sourced (path:line or doc section); nothing is invented. Use this skill when the user mentions "existing project", "legacy codebase", "reverse engineer", "import existing code", "brownfield", "we already have code", "onboard existing project", or when the user wants to enter the V-Model workflow but artifacts do not exist yet.

Transforms business analyses into epics, features, and tech-agnostic success criteria. Creates handoff documents for the architect. Use this skill when the user mentions "Requirements", "RE", "Define Features", "Create Epics", "User Stories", "Requirements", "Success Criteria", "NFRs", "ASRs", "Acceptance Criteria", or similar. Also when a BA document exists and the next step is the formalization of requirements.

Defines project structure, naming conventions, and way of working for all projects. Referenced by other skills to ensure consistent directory structures, file names, and documentation standards. Use this skill when the user mentions "project setup", "project structure", "conventions", "init", "initialize project", "directory structure", or similar. Also automatically relevant when starting a new project.

Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's comprehensive "Signs of AI writing" guide. Detects and fixes patterns including: inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, passive voice, negative parallelisms, and filler phrases.

Activates, reconfigures, or deactivates the Digital Innovation Agents workflow in a project. Writes the .dia/config.toml settings file and manages anchor blocks in agent-facing files (CLAUDE.md, AGENTS.md, GEMINI.md, .cursorrules, .github/copilot-instructions.md, .windsurfrules). Use this skill when the user mentions "DIA aktivieren", "DIA installieren", "DIA initialisieren", "DIA setup", "DIA settings", "Workflow-Modus", "Modus wechseln", "DIA off", "DIA deaktivieren", "Plugin aktivieren". Single skill that covers both first-time activation and later reconfiguration; the skill detects which path applies from the presence of .dia/config.toml.

Convenience wrapper for existing DIA users upgrading between DIA versions (e.g. v1 -> v2 -> v3). Runs the migration scripts under `tools/migration/` in sequence: detect state, strip status duplicates, rename IDs (FEATURE-NNNN -> FEAT-EE-FF, EPIC-NNN -> EPIC-NN), flatten analysis/, regenerate BACKLOG.md, update skill-name references, run `/consistency-check` mode A. Idempotent. Use this skill when the user already has DIA artefacts and wants to upgrade to current conventions without the full reverse-engineering walk. Triggers: "migrate to DIA v2", "migrate v1", "upgrade DIA", "convert backlog", "restructure backlog", "FEATURE to FEAT". For BROWNFIELD projects (no `_devprocess/` yet, only code), use `/reverse-engineering` instead -- it absorbs the same migration mechanics for any pre-existing partial artefacts and additionally walks the code to fill the gaps.

Guides users through the V-Model workflow: takes stock of the current project state, recommends the next phase skill, audits handoff entries for completeness, and runs the Closing Handoff after a successful security audit. The guide does not perform CRUD work on artifacts; every concrete change lives in the phase skill it dispatches to. TRIGGER when the user asks "where do I start", "what comes next", "I am lost in the workflow", "which phase fits", "wo bin ich gerade", "wo soll ich anfangen", "was kommt jetzt", or explicitly requests the V-Model overview or end-to-end orientation. DO NOT trigger for individual phase work (use the specific phase skill instead: business-analysis, requirements-engineering, architecture, coding, testing, security-audit), generic mentions of "workflow", "process", or "next step" inside an already-running phase skill, or when a phase skill is already active.

Bootstrap context for the Digital Innovation Agents V-Model workflow. Auto-loaded at session start by the SessionStart hook (unless mode = off). Carries the entry-point catalog, the helper-script path resolution rule, the activation contract, and opt-out behaviour. The user does not invoke this skill manually.

Verifies the V-Model artifact graph is intact: BA sections, Epics, Features, Success Criteria, ADRs, arc42 sections, PLANs, Backlog, Wayfinder rows, and code references. Two modes: syntactic (links, IDs, Refs) and semantic (content coherence via an agent). Default syntactic at the end of every skill phase. Semantic before release or on explicit request. Use this skill when the user mentions "consistency check", "graph check", "check references", "dead links", "orphan features", "graph-health", or when another V-Model skill completes a phase and wants to verify the artifact graph before handoff.

Handoff skill and bug-capture entry point: loads plan-context.md and all design artifacts, performs a critical review against the real codebase, and ensures continuous writeback to the artifacts during and after implementation. Also the entry point when a bug is reported outside of an active implementation run -- captures the FIX artefact (BACKLOG row + FIX detail file + branch) without forcing an immediate fix. Use this skill when the user mentions "implement", "code", "realize plan-context", "build feature", "Bug gefunden", "es gibt einen Fehler", "Fix erfassen", or similar, and either a plan-context.md / FEATURE spec exists OR a bug surfaced. This skill does NOT take over the coding workflow -- the Default Claude Code agent remains responsible for the actual implementation. This skill ensures the context is critically reviewed, cleanly handed off, and artifacts stay up to date.

Conducts structured business analyses: problem and stakeholder analysis, as-is/to-be gap analysis, user personas, scope definition. Creates BA documents as the foundation for requirements engineering. Uses innovation phases EXPLORATION, IDEATION, and VALIDATION. Use this skill when the user mentions "Business Analysis", "BA", "Stakeholder Analysis", "Problem Analysis", "As-Is Analysis", "Gap Analysis", "User Personas", "Define Scope", "Analyze Project", "Explore", "How might we", "Value Proposition", "Idea Potential", "Innovation", or similar. Also when the user wants to start a new project and does not yet have a clear requirement. This skill helps understand the problem before discussing solutions.

Creates Architecture Decision Records (ADRs) in MADR format and arc42 documentation. Generates plan-context.md as the context bridge to Claude Code. Use this skill when the user mentions "architecture", "ADR", "arc42", "Architecture Decision", "tech stack", "solution design", "system design", "architecture review", "plan-context", or similar. Also when requirements exist and the next step is technical structuring. This skill creates PROPOSALS. Claude Code makes the final decisions based on the real state of the codebase.