№ C121·30C4 · Soul · Coding pair
Sets up an agent that only plans: it breaks engineering tasks into small, testable subtasks ordered by dependency and never implements them.
SOUL.md
You decompose engineering tasks into small, testable subtasks.
Output a numbered list of subtasks. Each subtask should be:
Do not implement. Only plan.
№ 08E9·079F · Coding pair
★ 8Sets up a triage agent that removes noise from bulk security findings, merges duplicates and related issues on the same locus, and assigns defensible CVSS scores and severity bands. It is a strictly procedural working style with no conversational voice.
№ 2BC4·FEB9 · Coding pair
★ 1A template-architect agent that maintains the Harness SDD framework's conventions, manifest-first and deterministic, and refuses shortcuts like hand-editing generated files or skipping checks. Its tone is direct, precise and terse, leading with constraints before solutions.
№ B8C1·3C1C · Coding pair
★ 25A focused QA agent that turns plain-English requirements into deterministic, CI-friendly end-to-end tests and diagnoses failures in a strict CATEGORY/REASON/FIX format. It sets rules on selectors, secrets and git safety, with no personality flourish.
№ F4D8·F27F · Coding pair
Sets up a strict documentation agent that reports only to the Tech Lead and updates API references, env examples, READMEs and changelogs after merges, documenting only verified, committed features. It never talks to the human stakeholder or changes application logic.
№ EB43·1BC2 · Business operator
★ 1Sets up a planning agent that turns issue requirements into falsifiable specs with invariants, protocols, files touched and complexity, then hands off to downstream agents. The working style is procedural and checklist-driven, with a reuse step for existing spec templates.
№ D008·A67C · Coding pair
★ 1Sets up Archie as the scaffolding agent in a builder pipeline, creating protocols, in-memory fakes, Hypothesis property tests and module skeletons from a Spec without writing implementation code. The working style is procedural and checklist-driven, with pipeline position and file conventions spelled out.