example-skill

Sterne0

Forks1

Aktualisiert29. April 2026 um 12:18

This description is intentionally long enough to satisfy the validator reliably.

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

Lincyaw

Lincyaw/workbuddy

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

Datei-Explorer

2 Dateien

SKILL.md

readonly

name	example-skill
description	This description is intentionally long enough to satisfy the validator reliably.

See references/guide.md for the detailed template.

Mehr aus diesem Repository

gleiches Repository

acceptance-criteria

Lincyaw/workbuddy

Reference for writing and evaluating acceptance criteria. Use when an AC is flagged as untestable, when the spec-review agent needs to judge testability, or when deriving ACs from a vague requirement. Trigger on: acceptance criteria, AC, testability, 验收标准, how to write AC, is this AC testable, untestable criterion.

2026-06-060

code-review-standards

Lincyaw/workbuddy

How to review code against a spec with structured per-AC verdicts. Use when reviewing a PR, verifying code fulfills acceptance criteria, or selecting between multiple parallel implementations. Trigger on: code review, review standards, PR review, 代码审查, 代码评审, review agent, per-AC verdict, structured review.

2026-06-060

engineering-workflow

Lincyaw/workbuddy

Overview of the engineering pipeline and how each stage connects. Use when an agent is confused about what stage it's in, what it should do next, or how its output feeds into the next stage. Trigger on: engineering workflow, pipeline, what stage am I in, what comes next, workflow overview, 工程流程, 开发流程, pipeline stage, stage transition.

2026-06-060

spec-writing

Lincyaw/workbuddy

How to write a design spec that downstream agents can implement and test against. Covers four composable methods: Use Case for interaction flows, Given-When-Then for behavioral scenarios, Design by Contract for function-level guarantees, and plain AC for simple tasks. Use when writing a spec, reviewing spec completeness, or when a dev/test-gen agent reports the spec is too vague. Trigger on: spec, 设计文档, 需求文档, 接口设计, write spec, design doc, acceptance criteria, use case, given when then, design by contract, 契约, 用例.

2026-06-060

test-design

Lincyaw/workbuddy

How to derive tests from a spec. Covers extracting test cases from Use Case extensions, GWT scenarios, and Design by Contract invariants. Core insight: the test oracle is an invariant — tests find their value in checking exception branches and properties that must always hold, not in re-stating the happy path. Trigger on: test generation, write tests, test design, integration test, 写测试, 测试设计, test from spec, test oracle, invariant, property test, 不变量.

2026-06-060

pipeline-monitor

Lincyaw/workbuddy

Monitor the workbuddy agent pipeline, detect stuck issues, zombie processes, and missed redispatches. Works for both the 3-unit bundle (supervisor + coordinator + worker) and single-process `serve`. Use when the user says 'monitor the pipeline', 'check workbuddy status', '监工', '看看跑完了没', or asks to watch issue progress.

2026-05-180