Using these agents
Synced from
default-profiles/docs/usage.md. The repository is the source of truth.
With outfitter setup
Section titled “With outfitter setup”outfitter setupOn a new machine this installs the default agent catalog. Outfitter records the immutable ai-outfitter/default-profiles Release Please tag shipped by that
CLI version.
Manual addition
Section titled “Manual addition”Add this repository to your outfitter settings:
default_agent: founderdefault_harness: pi
sources: - github: ai-outfitter/default-profiles ref: v1.1.0Use a published version tag; do not use a moving branch name.
Then sync and run:
outfitter syncoutfitter run engineeroutfitter run data-analystPersona reviews
Section titled “Persona reviews”This catalog pins ai-outfitter/community-profiles as a source, which
supplies the shared persona-reviewer agent and the persona-authoring /
persona-review skills. The founder profile selects both skills; the
engineer profile selects persona-review. Run the shared reviewer in its own
Outfitter process and keep the report as durable project context:
mkdir -p docs/persona-reviewsoutfitter run persona-reviewer -- \ --append-system-prompt docs/personas/platform-lead.md \ --print "Review the onboarding flow. @README.md" \ > docs/persona-reviews/platform-lead-onboarding.mdThe default founder agent carries the whole loop. It authors one portable
persona file per customer role with persona-authoring, then invokes the
persona-review skill to launch the same reviewer process and save its report
under docs/persona-reviews/:
outfitter run founder# "Author a platform-lead persona, review the README through persona-review,# and save the report under docs/persona-reviews/."The persona file is plain Markdown with no frontmatter, and pastes unchanged into web agents as stakeholder context. Format and story: Personas and Persona reviews.