By observo-ai
QA + product spec toolkit for the Observo test management platform (https://observoai.co). Bundles eight Claude Code skills: (1) observo-test-cases — generate test cases from a PRD / requirements doc and push them to Observo with sensible defaults (status=IN_REVIEW, assignee from .observo-toolkit.json); (2) requirements-testing — review a requirement / PRD / Jira ticket for ambiguity, completeness, conflicts, testability, and missing acceptance criteria, posting findings to Jira (if connected) or to console; (3) observo-code-verifier — optionally ground scenarios in actual source code before pushing (graceful degradation when no repo access); (4) observo-review-test-case — review one or more Observo test cases against a 15-criteria quality checklist, post per-issue review comments via MCP (scope CASE / FIELD / STEP), assign a 0–10 score, and flip status to STATUS_CHANGES_REQUESTED when comments were created; (5) prd — write a structured PRD from raw input (meeting transcripts, notes, feature descriptions), English body and headings by default (non-English body opt-in via .observo-toolkit.json:prd_language); (6) pw-generate — repo-agnostic Playwright `.spec.ts` generator: discovers the consumer repo's Playwright layout (spec dir, Page Object usage, selectors registry, fixtures, tier vocabulary) and generates tests wired to Observo via the `@observo:<code>` tag — works on any Playwright project, configurable via optional `.observo-toolkit.json` (legacy `.observo-pw.json` also accepted); (7) pw-run — runs Playwright (or reuses fresh results.json) and writes results back to Observo: per-case status, per-step status (when step counts match), screenshot/trace/video attachments on FAILED, and the full results.json as a run-level event-log attachment. Always emits a 4-bucket coverage report (Linked/Unautomated/Unlinked/Stale) at the end; coexists with in-repo observo-reporter.ts by detecting the sidecar `.observo-metadata.json`; (8) observo-toolkit-bootstrap — record one plugin_install Layer 2 telemetry event per consumer repo, gated on .observo-toolkit.json:telemetry_enabled opt-in. Idempotent (marker file at .observo-toolkit/.install-seeded); re-fires only when the plugin version changes. Universal Playwright best practices enforced across pw-generate and pw-run: data-testid/getByRole selectors, no waitForTimeout, `@observo:<code>` tag as the single hardcoded join key.
Verifies a set of designed test scenarios against actual source code before they are pushed to Observo (or any other test management platform). Checks endpoint paths, error message strings, validation rules, and field names against handler code, proto files, and validators. Gracefully degrades when source code is not accessible (e.g., when invoked by a QA team without repo access) — in that case, returns the scenarios unchanged and clearly flags that verification was skipped. Use when you have a draft set of scenarios derived from a PRD / requirements doc and want to ground them in the actual implementation before recording them anywhere. Triggered by phrases like "verify test cases against code", "ground these scenarios in implementation", "check error messages match the code", "code-verify these tests", or invoked from observo-test-cases as an optional pre-create step.
Review one or more Observo test cases against a 15-criteria quality checklist, post per-issue review comments via MCP (scope CASE / FIELD / STEP), assign a compact 0–10 score, and flip status to STATUS_CHANGES_REQUESTED when comments were actually created. Use when the user asks to "review test case", "rate the quality of cases in suite X", "score test cases", or otherwise wants a systematic QA pass on an Observo case.
Generate test cases for a feature, requirement, or PRD and push them to the Observo test management platform with sensible defaults — status=IN_REVIEW and assignee = current user. Use when the user asks to "create test cases", "write test cases", "push test cases to Observo", "test cases for <module/requirement>", or similar. If the user did not explicitly say whether they want Observo records or local Jest/RTL/Playwright code, ask first via AskUserQuestion before doing anything.
Record one plugin_install telemetry event per consumer repo, idempotently. Reads `.observo-toolkit.json:telemetry_enabled` as the opt-in gate (default false) and `.claude-plugin/plugin.json:version` for the version field. Writes a marker file `.observo-toolkit/.install-seeded` so subsequent invocations are a no-op until the plugin version changes. Use when the user asks to "set up observo-qa-toolkit", "initialize observo plugin telemetry", "bootstrap observo toolkit", or as a one-time first-run step after enabling telemetry. The skill is privacy-first — when the opt-in flag is false or absent, the skill exits silently and records nothing.
Write a structured PRD from raw user input — meeting transcripts, notes, or feature descriptions. Default English body and English section headings; non-English body opt-in via `.observo-toolkit.json:prd_language`. Use when the user asks to "write a PRD", "draft a PRD", "write a PRD for <feature>", "PRD from this transcript / these notes", or provides meeting notes / requirements text expecting a structured product spec back. Default save location: `<prd_save_dir>` from `.observo-toolkit.json`, fallback `./docs/PRDs/<feature-name>.md`.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
npx claudepluginhub observo-ai/claude-plugins --plugin observo-qa-toolkitComprehensive skill pack with 66 specialized skills for full-stack developers: 12 language experts (Python, TypeScript, Go, Rust, C++, Swift, Kotlin, C#, PHP, Java, SQL, JavaScript), 10 backend frameworks, 6 frontend/mobile, plus infrastructure, DevOps, security, and testing. Features progressive disclosure architecture for 50% faster loading.
Complete creative writing suite with 10 specialized agents covering the full writing process: research gathering, character development, story architecture, world-building, dialogue coaching, editing/review, outlining, content strategy, believability auditing, and prose style/voice analysis. Includes genre-specific guides, templates, and quality checklists.
A growing collection of Claude-compatible academic workflow bundles. Covers scientific figures, manuscript writing and polishing, reviewer assessment, citation retrieval, data availability, paper reading, literature search, response letters, paper-to-PPTX conversion, and evidence-grounded Chinese invention patent drafting. Rules are organized as reusable skill folders with explicit workflows and quality checks.
Tools to maintain and improve CLAUDE.md files - audit quality, capture session learnings, and keep project memory current.
Intelligent draw.io diagramming plugin with AI-powered diagram generation, multi-platform embedding (GitHub, Confluence, Azure DevOps, Notion, Teams, Harness), conditional formatting, live data binding, and MCP server integration for programmatic diagram creation and management.
Persistent file-based planning for AI coding agents. Crash-proof markdown plans (task_plan.md, findings.md, progress.md) that survive context loss and /clear, with an opt-in completion gate and multi-agent shared state. Manus-style. Works with Claude Code, Codex CLI, Cursor, Kiro, OpenCode and 60+ agents via the SKILL.md standard. Includes Arabic, German, Spanish, and Chinese (Simplified and Traditional).