606 skills · sorted by relevance
Evaluate code against a product requirements document, scoring implementation and tests separately for each acceptance criterion. Produce an evidence-backed final grade, identify gaps, and compare implementations using a fixed checklist and scoring method.
Turn a Seed specification into GitHub issues for team planning. The skill creates a parent issue and implementation tasks, distributes acceptance criteria across them, and links the tasks in a progress checklist.
Convert agreed goals, constraints, and success criteria into a Seed specification an agent can execute and verify. A quality review checks consistency and testable outcomes, with any suggested refinements left for the user to approve.
Turn a multi-file development task or technology migration into a specification with acceptance criteria, then launch background implementation and verification. The workflow clarifies missing requirements, reviews the specification, and tracks progress and blockers through linked jobs.
Prepare conference slides, academic posters, and research promotion drafts from an accepted paper. The skill guides presentation timing, visual layout, and platform-specific writing while keeping claims and links tied to verified research materials.
Retrieve shared reference files and send work in progress using local shared paths. The skill also guides missing-file checks and distinguishes manual file transfers from synchronization already handled by task acceptance and submission.
Clarify responsibilities in a TeamHarness team, including planning, task execution, result acceptance, and runtime administration. Use the role boundaries to identify who owns each action and how participants should handle sensitive information.
Create a product requirements document for a new feature or product. Clarify users, problems, goals, and constraints, then organize prioritized requirements, acceptance criteria, implementation phases, and risks into a structured document for AI-assisted development.
Turn a rough app or automation idea into a detailed specification through guided interviews and research. Clarify user journeys, data, security, operations, and competing priorities, then document requirements and acceptance criteria for implementation.
Turn a feature description and project guidance into a requirements document with testable acceptance criteria. Review coverage, ambiguity, and scope before saving, using EARS, a structured format for describing system behavior and conditions.
Plan, run, and verify Jetson video encoding, decoding, transcoding, and segment workflows using NVIDIA samples or PyNvVideoCodec. It checks file hashes, byte sizes, frame counts, and logs to confirm that each stage consumes the preceding stage’s output.
Add unit and end-to-end browser tests to a completed development phase using its acceptance criteria, planning documents, and implementation. Review the proposed coverage, verify tests fail and then pass, and commit the generated test files.
Für Reisebedingungen: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt. Fachgebiet: AGB-Recht-Prüfer. Route: reisebedingungen-reseller-agb-risk-acceptance.
The English summary is being prepared. Showing the original description.
Für Risk Acceptance Memo: erstellt Entwurf mit Antrag, Beweis und Anlagen; Ergebnis: Schriftsatz mit Begründungs- und Anlagenlogik.
The English summary is being prepared. Showing the original description.
Guide real-build acceptance: literal taps, real inputs, expected outcomes, worst case first, one sitting. Triggers: testflight, human pass, acceptance test, before we ship, what should I test, release checklist, device test.
The English summary is being prepared. Showing the original description.
Write complete, ready-to-pull work items for an issue tracker: bugs, tasks, stories, spikes, and epics, each with the fields, attachments, and done test its type requires. Use this skill whenever the user wants to write a ticket, create a Jira issue, Linear issue, or GitHub issue, file a bug report, write a user story or acceptance criteria, scope a spike, open an epic, or break work into tasks. Triggers on write a ticket, create an issue, file a bug, bug report, user story, spike, epic, task breakdown, turn this into tickets, break this down, acceptance criteria, definition of ready, ready for dev, backlog item, capitalization stage. Also triggers when the user pastes a PRD, a spec, or a bug description and asks what to do with it, even if they never say the word ticket.
The English summary is being prepared. Showing the original description.
Validation-first design for Cavekit — every kit requirement must be automatically verifiable. Six-gate validation pipeline, phase gates, merge protocol, completion signals, acceptance criteria patterns. Use when designing acceptance criteria, wiring CI gates, or debugging why an agent is producing output that nobody can verify.
The English summary is being prepared. Showing the original description.
Terraform provider acceptance test patterns using terraform-plugin-testing with the Plugin Framework. Covers test structure, TestCase/TestStep fields, ConfigStateChecks with custom statecheck.StateCheck implementations, plan checks, CompareValue for cross-step assertions, config helpers, import testing with ImportStateKind, sweepers, and scenario patterns (basic, update, disappears, validation, regression), and ephemeral resource testing with the echoprovider package. Use when writing, reviewing, or debugging provider acceptance tests, including questions about statecheck, plancheck, TestCheckFunc, CheckDestroy, ExpectError, import state verification, ephemeral resources, or how to structure test files.
The English summary is being prepared. Showing the original description.
Design mandates for acceptance tests - hexagonal boundary, business language abstraction, user journey completeness, pure function extraction, 3 Pillars (domain language / chained narrative / production composition), and the layered ATD discipline (Universe-bound assertion, layer-dependent PBT mode, two-tier acceptance, example-based sad paths)
The English summary is being prepared. Showing the original description.
Acceptance test creation methodology for the DISTILL wave. Domain knowledge for the acceptance designer agent: port-to-port principle, prior wave reading, wave-decision reconciliation, graceful degradation, and document back-propagation.
The English summary is being prepared. Showing the original description.
Builds, updates or retires scoped acceptance tests and verifies execution; does not repair product code.
The English summary is being prepared. Showing the original description.
Standardize PRD discovery and drafting for product scope, user outcomes, requirement IDs, and acceptance criteria. Use when creating PRD, product requirements, feature specification, or acceptance criteria plan.
The English summary is being prepared. Showing the original description.
Trigger only when the user explicitly requests live Jira or Zephyr retrieval, existing-link inspection, linking authored test cases, label updates, or stale-link audits. Do not trigger for analysis-only prompts such as 'Analyze the acceptance criteria for TICK-4521', supplied acceptance criteria, test-case authoring, or AC-to-test generation.
The English summary is being prepared. Showing the original description.
Post-acceptance conference preparation workflow covering presentation slides, academic posters, and promotion content. Triggers on "scholar publish", "conference preparation", "prepare presentation", "create poster", "write promotion", "post-acceptance".
The English summary is being prepared. Showing the original description.