菜单
Enforced RED-GREEN-REFACTOR test-driven development. Use when implementing any behavior change that can be expressed as a test — new features, bug fixes, edge cases. The test MUST fail first; a test that passes on first run proves nothing.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/aiosbrain/aios-workspace --skill tdd-fail-first命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Manage the AIOS Linear board (the ONLY PM tool — Plane is retired). Use whenever updating, reading, or commenting on AIOS Linear issues (identifiers like AIO-72, AIO-75), the brain→PM projection-tracking epic, or the backlog. Triggers on "update AIO-NN", "the Linear board", "the AIOS board", "projection tracking issue", "/aios-linear". Provides a terse `linear.mjs` CLI so issue edits are one fast command instead of ad-hoc GraphQL one-liners. DO NOT use the Plane MCP for AIOS work — it is retired and its tools return huge irrelevant payloads.
Use YOUR own Slack to act as you — send messages and DMs to teammates, read your channels/DMs, and react — via the `slack` CLI (a zero-dependency tool that talks straight to the Slack Web API with your USER token). Messages post AS you and replies land in your own DMs. This is the INDIVIDUAL "act as me" connector — distinct from the team's read-only Slack history ingestion. Use when the user asks to message/DM a teammate on Slack, read a Slack thread/DM, or react. Requires Slack connected (run `aios connect slack`).
Verify that a fix or change actually did what it was for, before reporting that it works. Use before any "it works", "verified", "fixed", "confirmed", or "done" about something that was previously broken — and whenever a hook or a reviewer asks you to re-check a claim. Catches the failure where you measure a proxy (a neighbouring count, an absence of errors, a ratio) instead of the property the change exists to produce.
基于 SOC 职业分类
正在显示 SKILL.md
| name | tdd-fail-first |
| description | Enforced RED-GREEN-REFACTOR test-driven development. Use when implementing any behavior change that can be expressed as a test — new features, bug fixes, edge cases. The test MUST fail first; a test that passes on first run proves nothing. |
| source | Jesse Vincent (obra) — Superpowers enforced TDD |
| am_pattern | B2, B4 |
| triggers | ["tdd","test-driven","fail first","write the test first","red-green"] |
You are implementing with fail-first TDD. The non-negotiable rule: you must watch the test fail before you make it pass. A test written after the code, or a test that passes immediately, is not evidence — it may be testing nothing.
For a bug, the RED step is a reproduction test: a test that fails on the current code because of the bug, and encodes the expected correct behavior. Never fix a bug without one — a fix without a failing repro test can't prove it fixed anything, and the bug can silently return.
AGENTS.md (Commands section) — never guess.