Skip to main content

capitalone/context-specs

SkillsMP has collected 14 skills from capitalone/context-specs. Open a skill to review its source and details.

Latest recorded source activity
SkillsMP catalog refreshed
skills collected
14
GitHub stars
38
GitHub forks
6

Skills in this repository

Showing 14 of 14 collected skills.

occupation
Software Developers
description

One-time setup of a project as a harness ENVIRONMENT — the Software 3.0 half that follows `context-specs add`. Generates the project-specific artifacts an LLM must read the repo to write (AGENTS.md, bootstrap-worktree.sh, local-checks.sh), installs the…

updated
occupation
Software Developers
description

The harness concierge for improving a project's context — the human-in-the-loop expert on every context lever (the codebase's own shape, AGENTS.md, the Expert long-term memory, /intent, local-check lints) and on STUCK forensics. Use to resolve a STUCK PR…

updated
occupation
Software Developers
description

Resolve the outcome of `context-specs update` — walk every file where your edits and the new upstream version disagree, and decide keep / take / merge / customize with the consequence of each spelled out. Use after `context-specs update` reports conflicts or…

updated
occupation
Software Developers
description

This project's long-term memory — how to run, validate, and extend it; its architecture, patterns, hard invariants, worked examples, and current decisions/direction. Consult when planning a feature, validating a spec, implementing a slice, or writing intent…

updated
occupation
Software Developers
description

Update the project's long-term memory after a merge to main. Reads the merged diff and reconciles the current memory — adding, editing, and deleting Expert reference files — then drafts candidate lints and AGENTS.md pointers. Opens a reviewable learn/<sha>…

updated
occupation
Software Developers
description

Reads a PRD (`prds/<feature>/prd.md`) plus its executable `run-prd-test.sh` (and any helper artifacts under `prds/<feature>/`), grounds them in codebase research, and produces `specs/<feature>/mainspec.md` plus dependency-ordered slices. Encodes the runner as…

updated
occupation
Software Developers
description

Patch the code so `scripts/local-checks.sh` passes, after /implement-mainspec — a narrow post-implement polish specialist. Reads the (remediation-rich) check failures, fixes the underlying cause, never silences a check, re-verifies, and commits. Invoked…

updated
occupation
Software Quality Assurance Analysts & Testers
description

Evaluate a PR the harness produced — walk the change, run the system together, and build a firm understanding before you merge it. Use after the harness hands a converged PR to you for review (the "Ready for your review" comment), or any time you want to…

updated
occupation
Software Quality Assurance Analysts & Testers
description

Respond to an automated reviewer's findings on the current feature PR — a narrow, headless responder. Triages each reviewer finding into Clear / Ambiguous / Complex / Out-of-PRD-Scope, then acts — fixes the cause and pushes (diff-only) for Clear, posts one…

updated
occupation
Software Developers
description

One-time, guided setup of a standalone LLM-maintained wiki — a Karpathy "LLM Wiki" style knowledge base for a problem domain and your general architecture best practices. Scaffolds an external wiki vault (its own git repo) with /ingest, /query, /lint commands…

updated
occupation
Software Developers
description

Implements a mainspec end-to-end by delegating each slice to a `slice-implementer` subagent in dependency order, committing to `feature/<feature>` directly. Agent-first — invoked headless by the harness dispatcher with the feature slug. No human-in-the-loop,…

updated
occupation
Software Developers
description

Implements a single slice with unit tests and a Reflect step. Agent-first — invoked by the slice-implementer subagent (under implement-mainspec). No human-in-the-loop.

updated
occupation
Software Developers
description

Validates a mainspec and its slices via 3-subagent consensus plus expert review, then *applies* impactful fixes directly to the spec files. No human-in-the-loop summary or approval — agent-first. Touches `specs/<feature>/.validated` as its final committed…

updated
occupation
Software Developers
description

Turn an open-ended idea into a PRD plus a runnable definition of done. Use when a developer wants to start a new feature, "file a PRD", "spec out" or "scope" an idea, think through what to build, or kick off the harness for a piece of work. Produces…

updated
Showing 14 of 14 collected skills.