Loading...
Loading...
Found 82 Skills
Use when you need to locate the current spec pack (FEATURE_DIR) in the Spec process of sdlc-dev, avoid reading or writing requirements/*.md in the wrong directory, or encounter issues such as "misreading context/writing to the wrong file/non-compliant branch".
Use when you need to perform I2 (Implementation Execution) in the Spec Pack of sdlc-dev, implement in batches with `{FEATURE_DIR}/implementation/plan.md` as the only SSOT, run minimal verification, write back audit information, and report at batch checkpoints; stop immediately when encountering blocking or clarification required items.
Use this when you need to execute the AI SDLC (Spec Pack) process in the sdlc-dev repository, select/chain together skills from the demand side (raw/solution/prd/prototype/demo) and implementation side (plan/execute/finishing), and use guardrails to avoid context drift, incorrect directory writes, or skipping critical steps under pressure.
Bring existing tracker issues up to standard without implementing anything — applies missing SDLC labels, clarifies laconic issues (analyzing attached screenshots), posts a read-only implementation-prep analysis, and flags feature issues lacking a covering spec (optionally authoring one with --write-missing-specs). Single issue by id, or a batch (default — last ~25 open, worst-described first). Idempotent and claim-aware. Use for "triage the backlog", "clean up issue 123".
AI SDLC QA workflow. Use when an AI assistant is asked for QA planning, acceptance validation, regression scope, exploratory checks, smoke tests, release verification, or change-focused manual validation evidence. Supports `--quick-flow` for fast assumption-driven execution and `--full-flow` for question-driven verified execution. Explicit full or end-to-end spec refinement requests continue through the existing 18-stage refinement cascade.
AI SDLC backend validation workflow. Use when an AI assistant needs to validate Go, SQL, API, provider integration, SDD, or documentation changes in this repository and choose focused deterministic checks without running unrelated expensive tests by default. Supports `--quick-flow` for fast assumption-driven execution and `--full-flow` for question-driven verified execution.
AI SDLC test-case-driven testing workflow. Use when an AI assistant is asked to derive test cases, create a test plan, expand coverage, or write tests from explicit scenarios before implementing unit, service, transport, or integration tests. Supports `--quick-flow` for fast assumption-driven execution and `--full-flow` for question-driven verified execution. Explicit full or end-to-end spec refinement requests continue through the existing 18-stage refinement cascade.
Generate Testing & Quality documentation for SDLC projects. Compliant with BS ISO/IEC/IEEE 29119-3:2013 (supersedes IEEE 829:2008 and BS 7925-2:1998). Covers Software Test Plan, Test Case Specifications (with normative 29119-3 fields), V&V Plan...
Autonomously turn a brief or FR issue into a spec landed on a ready PR — runs om-spec-writing --autonomous (defaults posted for override), attaches UI mockups and current-app screenshots as PR evidence when a browser provider exists, applies full SDLC labels, and emits PR/spec markers for chaining into om-auto-implement-spec. Use for "write a spec for X and open a PR", "spec this issue".
Use when you need to execute I2 (Implementation Execution) in the Spec Pack of sdlc-dev, using `{FEATURE_DIR}/implementation/plan.md` as the sole SSOT to implement in batches, run minimal validation, write back audit information, and report at batch checkpoints; stop immediately when encountering blocks or clarification items.
Launch Loki Mode autonomous SDLC agent. Handles PRD-to-deployment with minimal human intervention. Invoke for multi-phase development tasks, bug fixing campaigns, or full product builds.
Use this when you need to initialize a new Spec Pack in the AI SDLC workflow of this repository (create a three-digit numbered branch and the `.aisdlc/specs/{num}-{short-name}` directory), or when you are unsure about input parsing, short name rules, UTF-8 BOM file path parameter passing, script invocation methods, or output artifacts when executing `spec-init`.