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",…

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

How to create, refine, split, estimate, prioritise and link Product Backlog Items (PBIs) in Skald. Covers PBI types (Feature / Bug / Refactor / Spike) and title shapes, S/M/L/XL sizing calibrated for AI-assisted delivery, the variable PBI↔requirement…

How to write, refine, split and manage requirements in Skald — the living specs in Spec-Driven Development. Covers user-story and EARS title shapes, the Example Mapping workshop (story → rules → examples → questions; Specification by Example), Gherkin with…

How to model a product's domain in Skald — the domain hierarchy, and the ubiquitous language as Entities, Processes and Terms. DDD-inspired but simpler: a clear tree of domains, each holding the glossary it owns. Covers the 3-level depth cap, when to nest vs…

How to set and track OKRs (Objectives and Key Results) in Skald, following the Perdoo methodology. Covers the Time Period → Objective → Key Result → Check-in hierarchy, qualitative Objectives vs measurable Key Results, the outcome-not-output rule, the ≤5 KRs…

Your Skald health check — what to do next in a product. Read-only scan across every layer (Vision, Users, Domains, Glossary, Requirements with rules and examples, Backlog Items with linkage and sizing, Goals/OKRs, UX research), an opinionated view of what is…

Spec-Driven Development (SDD) in Skald — requirements as the living specs that drive delivery. The requirement is the spec; one PBI is one change; per-feature spec files are derived at delivery time and disposable. Covers the two-layer truth model, status…

How to draft and maintain a product's Vision and User list in Skald, using Roman Pichler's Product Vision Board as the interview — Target Group → Needs → Product → Business Goals, distilling the Vision statement last. The stored Vision is short Markdown…

Why Skald exists and what it changes for a product manager — use when someone asks what Skald is for, what makes it different from a backlog tool plus a wiki, why they should move their product into it, or says some version of "I don't see what's new". Also…

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.

Use when a work item has a task list and needs building. The user asks to implement LEGE-3 or ITEM-2, build the tasks, make the scenarios pass, continue implementing, or asks what comes after sdd-tasks. Last step of the kit: spec, plan, tasks, implement.…

Use when a feature request needs turning into a spec. The user pastes a feature request, names a work item such as LEGE-3 or ITEM-2, asks to specify, define or write requirements, rules, examples, scenarios or acceptance criteria, or says 'spec this'. First…

Use when a work item has a finished spec and needs a plan. The user asks to plan LEGE-3 or ITEM-2, asks how to build it, wants options compared, or asks what comes after sdd-spec. Second step of the kit: spec, plan, tasks, implement. Weighs two ways to build…

Use when a work item has an approved plan and needs a task list. The user asks for tasks for LEGE-3 or ITEM-2, wants the plan broken down, or asks what comes after sdd-plan. Third step of the kit: spec, plan, tasks, implement. Writes .sdd/<ID>/tasks.md, one…