pssah4
- 13 skills
- 0 followers
- 11 hours ago last updated
- ▌ Coding · pssah4 bundleHandoff and bug-capture skill: loads plan-context and design artifacts, reviews them critically against the real codebase, and keeps artifacts in sync during and after implementation. TDD is the default. Use for "implement", "code", "build feature", "realize plan-context", "Bug gefunden", "es gibt einen Fehler", "Fix erfassen".
- ▌ Testing · pssah4 bundleCreates and manages unit and integration tests: detects the test framework, follows project conventions, runs the fix-loop. Use when the user mentions "write tests", "unit tests", "integration tests", "test coverage", "tests missing", "TDD", or after implementation when tests need creating or updating.
- ▌ Dia Guide · pssah4 bundleGuides users through the V-Model workflow: takes stock of the project state, recommends the next phase skill, audits handoff state, and runs the Closing Handoff after a green security audit. Explicit user command for "where do I start", "what comes next", "wo bin ich gerade", "was kommt jetzt". Never for individual phase work.
- ▌ Dia Setup · pssah4 bundleActivates, reconfigures, or deactivates the DIA workflow in a project. Writes .dia/config.toml (mode + profile) and manages anchor blocks in agent files (CLAUDE.md, AGENTS.md, ...). Use for "DIA aktivieren", "DIA setup", "DIA settings", "Modus wechseln", "Profil wechseln", "DIA off". Covers first-time activation and later reconfiguration.
- ▌ Humanizer · pssah4 bundleRemove signs of AI-generated writing from text. Use when the user says "humanize", asks to check text for AI-Sprachmuster, wants to remove signs of AI writing, or says "Text prüfen". Detects and fixes inflated symbolism, AI vocabulary, em dash overuse, negative parallelisms, filler phrases, and related patterns.
- ▌ Dia Realign · pssah4 bundleOne entry point for repos that predate current DIA conventions: brownfield onboarding (existing codebase, legacy code, reverse engineer, we already have code) and legacy DIA upgrades (migrate v1/v2, upgrade DIA, FEATURE to FEAT, restructure backlog). Detects repo state, then runs a reverse walk, a script pass, or a gap walk.
- ▌ Architecture · pssah4 bundleCreates architecture decision records (post-hoc by default, full MADR for constraints), the arc42 constraints doc, navigation artifacts (SYSTEM-MAP, decisions router), and plan-context.md as ref index. Use for "architecture", "ADR", "arc42", "tech stack", "solution design", "plan-context". Proposals only; /coding decides.
- ▌ Dia Bootstrap · pssah4Bootstrap 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.
- ▌ Security Audit · pssah4 bundleFormal full-codebase security audit producing a written report with prioritized findings: SAST, OWASP (incl. LLM Top 10), SCA, supply chain, Zero Trust. Trigger ONLY on explicit requests like "security audit", "OWASP audit", "Sicherheitsaudit", "dependency audit". NOT for PR-level checks, one-off questions, or generic "security" mentions.
- ▌ Business Analysis · pssah4 bundleCondenses a structured dialog about problem, users, and scope into a short BA record that feeds requirements engineering. Use when the user mentions "Business Analysis", "BA", "Problem Analysis", "Personas", "Define Scope", "Explore", "How might we", "Value Proposition", or starts a new project without a clear requirement.
- ▌ Consistency Check · pssah4Verifies the V-Model artifact graph: Epics, Features, ADRs, PLANs, Backlog, Wayfinder rows, code refs. Syntactic and semantic modes. Explicit user command for "consistency check", "graph check", "dead links", "orphan features", or before a release; routine enforcement runs via the pre-commit hook, not per phase.
- ▌ Project Conventions · pssah4 bundleDefines project structure, naming conventions, and way of working for all projects; other skills link here for the canonical specs. Use when the user mentions "project setup", "project structure", "conventions", "init", "initialize project", "directory structure", or starts a new project.
- ▌ Requirements Engineering · pssah4 bundleTransforms business analyses into epics, features, and tech-agnostic success criteria; creates the architect handoff. Use when the user mentions "Requirements", "RE", "Define Features", "Create Epics", "User Stories", "Success Criteria", "NFRs", "ASRs", "Acceptance Criteria", or when a BA exists and needs formalization.