Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

acceptance-tests

Sterne43

Forks7

Aktualisiert12. Mai 2026 um 15:57

Use when acting as `acceptance_test_writer` to propose happy-path acceptance and integration coverage from an approved spec or ExecPlan. Do not use to materialize tests directly or to edit production code.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

thegeronimo

thegeronimo/hyperopen

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

Softwarequalitätssicherungsanalysten und -testerInformatik- und Mathematikberufe·SOC 15-1253

SKILL.md

readonly

name	acceptance-tests
description	Use when acting as `acceptance_test_writer` to propose happy-path acceptance and integration coverage from an approved spec or ExecPlan. Do not use to materialize tests directly or to edit production code.

Acceptance Tests

Use this skill when acting as the acceptance_test_writer role for a multi-agent ticket.

Read First

/hyperopen/AGENTS.md
/hyperopen/docs/MULTI_AGENT.md
The current ticket ExecPlan under /hyperopen/docs/exec-plans/active/
/hyperopen/docs/QUALITY_SCORE.md

Job

Proposal pass only: design acceptance and integration tests from the frozen spec.
Focus on user-visible happy-path and integration behavior, not boundary or adversarial coverage.

Guardrails

Write only manager artifacts under /hyperopen/tmp/multi-agent/<local-run-key>/.
Do not materialize tests directly.
Never edit /hyperopen/src/**.

Expected Outputs

acceptance-tests.proposal.json

Mehr aus diesem Repository

gleiches Repository

bug-flow

thegeronimo/hyperopen

Invoke explicitly with `$bug-flow` for unclear bugs, regressions, or failure investigations that need structured diagnosis, regression tests, the smallest fix, and findings-first review. Do not use for obvious one-line fixes or planned feature work.

2026-05-1243

edge-case-tests

thegeronimo/hyperopen

Use when acting as `edge_case_test_writer` to propose adversarial, boundary, and invariant coverage that complements acceptance coverage. Do not use to materialize tests or edit production code.

2026-05-1243

feature-flow

thegeronimo/hyperopen

Invoke explicitly with `$feature-flow` for complex features, significant refactors, or multi-file behavior changes that need an ExecPlan, proposed test coverage, RED-phase failing tests, implementation, and review. Do not use for tiny fixes, doc-only work, or purely local cleanup.

2026-05-1243

spec-writer

thegeronimo/hyperopen

Use when acting as `spec_writer` to create or refresh the active ExecPlan, clarify scope, and record acceptance criteria for a multi-agent ticket. Do not use for production-code edits or standalone prose cleanup.

2026-05-1243

browser-mcp-explore

thegeronimo/hyperopen

Use Browser MCP for exploratory browser debugging, live-session inspection, parity compare, design review, and selector or flow discovery before converting stable paths into Playwright.

2026-04-0143

browser-qa

thegeronimo/hyperopen

Use when acting as `browser_debugger` to gather browser evidence, run the governed QA passes, and report PASS/FAIL/BLOCKED outcomes for UI-facing work. Do not use for application-code edits.

2026-04-0143

Jeden Skill mit einem Klick ausführen