Skip to content

feat(outfitter skill): proactive agentic-design advisor - #204

Open
ncrmro wants to merge 6 commits into
mainfrom
feat/outfitter-advisor-skill
Open

feat(outfitter skill): proactive agentic-design advisor#204
ncrmro wants to merge 6 commits into
mainfrom
feat/outfitter-advisor-skill

Conversation

@ncrmro

@ncrmro ncrmro commented Jul 23, 2026

Copy link
Copy Markdown
Contributor

Grows the always-on outfitter self-skill from a reactive documentation router into a proactive agentic-design advisor: it recognizes which of the ecosystem's patterns fit a user's project and applies them with Outfitter's primitives — so a non-expert gets good agentic design.

What changed (.outfitter/skills/outfitter/SKILL.md)

  • Advisor posture in the description + intro (proactive, but surfaces only the 1–2 highest-value patterns).
  • ## Agentic patterns — a project-signal → pattern → reference → apply map: CI issue-triage (actions), the recurring-runs graduation ladder, channel intake (channels), in-cluster residency (operator), few-agents-many-skills / skill-as-router, subagent delegation, ambient conventions, and org adoption (control catalog).
  • ## Audit a project — survey signals (repo type, .agents, CI, k8s, channels/creds, goal) → match → prioritized shortlist → offer to apply.
  • Operational — beyond the outfitter CLI, drive gh (workflow PRs) and kubectl (Organization/Agent CRs), with a guard: outfitter validate --strict + dry dump/run first, and confirm before any outward/irreversible action.
  • References/routing extended: conventions, recurring-runs, in-cluster, channels, usecases/organization-profile-catalog.

No new skill, no separate pattern library — the patterns are the docs the skill already ships. outfitter validate --strict passes.

Dependencies

  • Based on docs/post-v1-revamp (needs its conventions/recurring-runs/in-cluster docs). Retarget to main once that lands.
  • Bundles docs/documentation/channels.md (same content as the channels-docs PR); if that merges first, this reconciles trivially.

🤖 Generated with Claude Code

ncrmro and others added 6 commits July 22, 2026 20:45
…nd automation surfaces

Restructure the documentation entry points around a progressive journey
(start personal → understand → grow → automate → contribute):

- README: replace the stale legacy-profile status banner with the
  protocol pin, open with the force-multiplier why (the ladder and the
  surfaces), and link the philosophy and the journey index.
- docs index: tiered journey with a stated progressive-disclosure IA.
- conventions.md (new): place once, specialize downward, never copy;
  layer homes; ambient rule vs skill vs hook placement.
- recurring-runs.md (new): loops three ways — local loop extension,
  Actions cron, cluster CronJobs/resident — one primitive, three clocks.
- in-cluster.md (new): Link Operator primitives, execution shapes,
  channels.
- subagents.md: the four delegation boundaries plus adversarial-review
  and singleton-coordinator patterns.
- usecases (new, story-first): shared-conventions dedup,
  flaky-test post-mortems, grafana-alert-investigator,
  self-improving-skills.

Refs #197

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
… fragment

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…e referenced

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…atus labels, adapter caveats

- Correct override semantics everywhere they were overstated: ID-addressed
  resources merge by ID; root agents.md/system-prompt.md wins whole-file
  by layer precedence, with fragment-level override deferred to the
  conventions roadmap primitive.
- Restore a transition note (published CLI may lag these docs; Migration
  linked) and a surfaces-status caveat in the README.
- Label project-repos as an illustrative convention, not shipped catalog
  behavior; describe Claude porting/symlinks as the design tracked in #187.
- Reframe recurring runs as one composition/contract with different
  clocks and lifecycles; note the loop extension is loadout-selected,
  not bundled.
- Qualify CI transcript artifacts as optional and adapter-dependent.
- Mark the Link Operator page as a design preview (not yet public),
  drop dead links, and fix the delegation-boundary ordinal.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Semantic node ids throughout, self-closing <br/>, quoted labels,
autonumber on the run sequence, and labeled graduation edges on the
README ladder. Skill: ai-outfitter/community-profiles#9.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Grow the always-on `outfitter` self-skill from a reactive doc router into a
proactive advisor that recognizes which agentic-design patterns fit a user's
project and applies them — so a non-expert gets good agentic design.

- Description + intro reframed to an advisor posture (proactive, not noisy).
- New "Agentic patterns" section: project-signal → pattern → reference → apply
  (CI issue-triage, recurring-runs graduation ladder, channel intake, in-cluster
  residency, few-agents-many-skills, subagent delegation, ambient conventions,
  org adoption).
- New "Audit a project" section: survey signals, match patterns, present a
  prioritized shortlist, offer to apply.
- Operational apply surface: beyond `outfitter`, drive `gh` (workflow PRs) and
  `kubectl` (Organization/Agent CRs), with a guard — validate first, confirm
  before any outward/irreversible action.
- References + routing extended with conventions, recurring-runs, in-cluster,
  channels, and the organization-profile-catalog usecase.

Includes docs/documentation/channels.md so the channels pattern resolves; stacks
on the post-v1-revamp docs. outfitter validate --strict passes.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Base automatically changed from docs/post-v1-revamp to main July 24, 2026 05:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant