Menú
Add a Testing section to a feature flow document using the standard template.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
| name | add-testing |
| description | Add a Testing section to a feature flow document using the standard template. |
| allowed-tools | Read, Edit |
| user-invocable | true |
| argument-hint | <feature-flow-name> |
| automation | manual |
| metadata | {"version":"1.0","created":"2026-03-13T00:00:00.000Z","author":"Ability.ai","changelog":["1.0: Initial version — adds a Testing section to a feature flow document using the standard template."]} |
ℹ️ First, set expectations: before anything else, print one short line with this skill's version and its most recent change — the top entry of
metadata.changelogabove — e.g.add-testing vX.Y — recent: <summary>. Then proceed.
Add a Testing section to a feature flow document using the standard template.
| Source | Location | Read | Write | Description |
|---|---|---|---|---|
| Feature Flow | docs/memory/feature-flows/{name}.md | ✅ | ✅ | Target document |
/add-testing {feature-flow-name}
Read the feature flow document (docs/memory/feature-flows/{name}.md)
Add a Testing section before "Related Flows" using the template:
Use Edit tool to insert the section.
## Testing
**Prerequisites**:
- [ ] [Service/prerequisite 1]
- [ ] [Service/prerequisite 2]
**Test Steps**:
### 1. [Action Name]
**Action**:
- Step 1
- Step 2
**Expected**: What should happen
**Verify**:
- [ ] Check 1
- [ ] Check 2
### 2. [Next Action]
...
**Edge Cases**:
- [ ] Test scenario 1
- [ ] Test scenario 2
**Cleanup**:
- [ ] Cleanup step 1
**Last Tested**: YYYY-MM-DD
**Tested By**: Not yet tested
**Status**: Not Tested
**Issues**: None
Run a remote Trinity agent task in a sequential, bounded loop — a fixed number of iterations or until a stop signal, with optional response chaining. Fires server-side via run_agent_loop (caller can disconnect), then polls and renders progress. The remote, durable counterpart to Claude Code's local /loop. Add `local` to run the same bounded loop natively in this session instead — inline back-to-back iterations, or a hand-off to the built-in /loop when a cadence is given.
Make any agent a system-aware orchestrator — installs /discover-agents (discover the fleet from live Trinity and/or a repo list into a descriptive fleet/system-map.yaml), /compose-system (turn the map into a Trinity SystemManifest and deploy_system), and /orchestrate (route, fan out, and run ephemeral agents via Trinity MCP). Aligns with Trinity's existing SystemManifest; no parallel standard.
Create a new skill or playbook. Guides through requirements gathering and generates the appropriate template based on complexity.
Create an executive chief of staff agent — asks about your tools, team, and priorities, then scaffolds a Trinity-compatible agent for daily briefings, meeting prep, and decision tracking
Create a personal medical-records agent — bootstraps a profile from your existing health documents, then ingests new files, maintains structured memory, tracks lab trends, prepares doctor visits, and runs an evidence-based nutrition + supplement framework
Create a content writer agent — asks about your brand voice, platforms, and topics, then scaffolds a Trinity-compatible ghostwriter agent that writes in your voice