Skip to content

Vendor the cohort's agent skills: gregoryfoster/skills, obra/superpowers, a brainstorming override, the auto-refresh hook #3

Closed

Description

@gregoryfoster

Problem

Processor has none of the cohort's agent tooling. Every sibling vendors gregoryfoster/skills under skills-vendor/, and all but broker also vendor obra/superpowers. So reviews and ships here run without the cohort's shared checks, and nothing refreshes them.

Scope

This follows managing-skills, with broker#15 as the precedent for a sibling that bootstrapped after the fact.

  • Submodules skills-vendor/gregoryfoster-skills and skills-vendor/obra-superpowers
  • The selection below, symlinked into skills/ (agentskills.io) and .claude/skills/ (Claude Code)
  • skills/brainstorming override
  • .skills/doctor.sh
  • The auto-refresh SessionStart hook, both halves (symlink + .claude/settings.json entry)
  • Ruff skips skills-vendor/; .gitignore covers the worktree roots and .claude/settings.local.json
  • docs/SKILLS.md, an AGENTS.md pointer, and the PR workflow recorded as the repo standard
  • A test that pins the symlink layout and both halves of the hook

Selection

gregoryfoster-skills (11): the set archiver and replicator link, less init-project-fastapi. That is curating-context, enforcing-architecture, init-socraticode, managing-skills, orchestrating-issue-backlog, reviewing-architecture, reviewing-code-python-fastapi, shipping-work-python-fastapi, using-git-worktrees, using-mayfly-chat and writing-plans.

obra-superpowers (11 + 1 override): dispatching-parallel-agents, executing-plans, finishing-a-development-branch, receiving-code-review, requesting-code-review, subagent-driven-development, systematic-debugging, test-driven-development, using-superpowers, verification-before-completion and writing-skills, plus brainstorming as a local override.

Decisions

  • Review and ship use the -python-fastapi variants, though processor isn't a FastAPI service. Broker#15 did the same. The vendored pre-ship.sh runs exactly processor's gate (ruff check, ruff format --check, pytest minus integration) unmodified, so there is no pre-ship fork. The Click variant is another stack, and the stack-neutral one's pre-ship.sh is a stub.
  • The brainstorming override is a minimal redirect (observo's pattern). It is upstream v6.4.2 verbatim, except that docs/superpowers/specs/ becomes docs/specs/, where the spec already lives. visual-companion.md and scripts/ stay vendor symlinks. The heavier forks (archiver, replicator, watcher, notifier) have each needed re-sync issues.
  • Superpowers' using-git-worktrees and writing-plans are not linked. Their names collide with gregoryfoster's, which the cohort links. diagnosing-superpowers (new in v6.4.1) is linked by no sibling.
  • Left out: init-project-fastapi (a scaffolder), vendoring-openapi-client (processor calls no sibling HTTP API), auditing-ci-cost (no CI), and the other stack variants.
  • Changes land as issue, then branch, then PR. That is the standard for this repo from here on.

Not this issue

  • curating-context's weekly cadence and PostToolUse write guard; SocratiCode indexing; processor's row on upstream's .skills/cohort roster

Implemented in #4.

Activity

  1. added 8 commits that reference this issue on Sep 30, 2026
  2. gregoryfoster commented on Sep 30, 2026

    @gregoryfoster
    MemberAuthor

    Shipped in #4, merged as 33602c1.

    • gregoryfoster/skills (c90e3c2) and obra/superpowers (v6.4.2) are vendored under skills-vendor/, with 22 skills linked into both discovery paths plus the brainstorming override (a minimal docs/specs/ redirect).
    • The auto-refresh hook and the doctor are installed. install-refresh.sh --check exits 0 on main, and .skills/doctor.sh initialised the deployed checkout's submodules after the merge.
    • docs/SKILLS.md and AGENTS.md record the issue → branch → PR workflow, with the post-merge git pull --ff-only and the worktree recipe.
    • One CR round with seven findings, all fixed (in #3 Vendor the cohort's agent skills #4's description).

    Follow-ups:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions