Skip to main content

blakesims/stores

SkillsMP has collected 17 skills from blakesims/stores. Open a skill to review its source and details.

Latest recorded source activity
SkillsMP catalog refreshed
skills collected
17
GitHub stars
0
GitHub forks
0

Skills in this repository

Showing 17 of 17 collected skills.

occupation
Computer Systems Analysts
description

Use when operating as the Pi architecture/design governor for the stores substrate, or when asking Pi for design review, priority coherence, contract ratification advice, or architectural approval over agent-comm.

updated
occupation
Software Developers
description

Use when operating as the Claude Code engine controller for the stores substrate: driving tasks, daemon/worktrees, codex/rebase loops, and multi-agent coordination.

updated
occupation
Software Developers
description

Use for the temporary front-of-engine queue-curation role in stores: triages observations/intake/tasks, deduplicates stale/noisy rows, drafts priority recommendations, and delegates backlog analysis to subagents without implementing code.

updated
occupation
Software Developers
description

Use during wind-down when acting as engine-controller and preparing the next engine-controller agent handover.

updated
occupation
Software Quality Assurance Analysts & Testers
description

Use for the session-scoped read-only codex sensor role in stores: watches in_review tasks, rebases review worktrees, runs codex, and posts structured review digests over agent-comm without writing substrate state or code.

updated
occupation
Software Quality Assurance Analysts & Testers
description

Use during wind-down when acting as reviewer-runner and handing off codex/review state to the next reviewer-runner.

updated
occupation
Software Developers
description

Use during wind-down when acting as Pi architect and handing off architectural state, priorities, and pending decisions.

updated
occupation
Software Developers
description

Use when Blake says context is high, asks to wind down, pause/clear the engine, prepare handover, or end a multi-agent stores session cleanly. Coordinates substrate-agent/reviewer-runner feedback, updates SOP skills/docs, and produces next-session handover…

updated
occupation
Software Developers
description

File a substrate-friction observation correctly. Use the moment you notice anything unexpected about the substrate — a missing flag, a confusing error, a workflow surprise. Filing is autonomous; do not gate on the user.

updated
occupation
Software Developers
description

Single entry point for substrate-driven work. Reads the queue (open observations, blocked tasks, mid-flight tasks), proposes one action, awaits user assent. Use whenever the user wants to "do the next thing" in this repo.

updated
occupation
Software Developers
description

Promote an observation to a substrate task. User-authority moment (U2) — the human must be present and assenting. Use when an observation is T3 (anything bigger than ≤5 files / ≤200 LOC, or anything touching schema, runner contract, or substrate API).

updated
occupation
Software Developers
description

Wrap a completed task — read the synthesis brief and approve or reject.

updated
occupation
Software Developers
description

Walk Blake through pending gate items (decisions + scripts) one at a time, with AI assistance. Resolves the human-only inbox without context-switching.

updated
occupation
Software Developers
description

Quickly log something noticed mid-flow into the observations store. Triages first; only files when the fix isn't a T1 you can do right now.

updated
occupation
Software Developers
description

Pick the next open observation, classify it, and (for T3) capture the intent contract at the moment the user has context. Resolve in place when possible; spawn deeper agents only when needed.

updated
occupation
Software Developers
description

Drive the next workflow task to completion via Claude Code.

updated
occupation
Software Developers
description

Pull the highest-priority ready task from the tasks store and run it autonomously via tasks:start. The intent contract is already on the task row (set at creation time); no human pause needed before the executor starts.

updated
Showing 17 of 17 collected skills.