SmidigStorm

This skill should be used when the user asks to "install openclaw", "set up openclaw", "configure openclaw channels", "openclaw gateway", "openclaw troubleshooting", "add whatsapp to openclaw", "add telegram to openclaw", "openclaw agent", "openclaw models", "openclaw cron", "openclaw memory", "openclaw skills", "openclaw security", "openclaw browser", "openclaw sessions", "openclaw workspace", "openclaw docker", "openclaw not working", "debug openclaw", "connect discord to openclaw", "openclaw setup guide", or mentions openclaw setup, configuration, troubleshooting, or daily usage.

Write BDD requirements in Gherkin format. Guides the user through the process.

Guided implementation planning with codebase understanding and requirement focus

Manage tech stack and architecture decisions

Document domain knowledge including entities, processes, and ubiquitous language

Execute an implementation plan step by step

Manage product backlog as an ordered priority list

Create or update the product vision document

Apply DDD tactical patterns (Entities, Value Objects, Aggregates, Domain Services, Repositories) and strategic design (Ubiquitous Language, Bounded Contexts). Use when modeling complex business logic.

Apply Clean Architecture layering and dependency rules (Domain, Application, Infrastructure, Presentation layers). Use when structuring applications or ensuring dependencies point inward.

Write clear, testable requirements using User Stories and Gherkin scenarios. Capture functional and non-functional requirements with proper acceptance criteria. Use when defining new features or documenting system behavior.

Enforce SOLID principles (Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, Dependency Inversion) in object-oriented design. Use when writing or reviewing classes and modules.

Follow TDD practices with Red-Green-Refactor cycle. Write tests before implementation, use AAA pattern, and ensure high-quality test coverage. Use when implementing features or fixing bugs.

Follow trunk-based development practices with short-lived branches, frequent integration to main, feature flags, and continuous integration. Use when managing git workflow and releases.

PM Airtable data model reference. Use when creating tables, querying structure, or understanding relationships between Domain, Subdomain, Capability, Entity, Requirement, and BacklogItem tables.

Architecture Decision Records (ADRs) for documenting technical decisions. Use when creating, updating, or reviewing architecture decisions. Triggers on discussions about technical choices, trade-offs, or "why did we choose X" questions.

Document domain knowledge including entities, attributes, relationships, processes, and ubiquitous language. Use when documenting domain models, entity relationships, business processes, or building a glossary of domain terms.

Interactive implementation planning from backlog items. Use when creating plans for features, fixes, or tasks. Guides 6-phase collaborative dialogue from discovery through documentation.

BDD requirements using Gherkin syntax. Activates when users describe features, requirements, user stories, acceptance criteria, or work with .feature files. Generates Given-When-Then scenarios, validates Gherkin structure, and creates complete feature files.