Skip to content
Back to skills

Prime Context

ASecurity

Use before starting pipeline work on a Ready feature the agent hasn't worked yet. Triggers — "/engineer.prime-context", "prime context", "load context before we start", "get up to speed on feature X".

  • 150 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added May 26, 2026
development

Security analysis

A100/100

Scanned May 27, 2026

npx -y skills add swingerman/disciplined-agentic-engineering --skill prime-context --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Prime Context?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Prime Context
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/swingerman-prime-context/badge)](https://www.skillsdirectory.com/skills/swingerman-prime-context)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: prime-context
description: Use before starting pipeline work on a Ready feature the agent hasn't worked yet. Triggers — "/engineer.prime-context", "prime context", "load context before we start", "get up to speed on feature X".
---

# prime-context

Load working memory before pipeline work on a Ready feature — the convergent counterpart to `discuss`. Forked from `superpowers:brainstorming` but inverted: no exploration, just loading and orienting. Produces no artifact.

## When to use

A prep step (not a checkpoint) between `feature-init` and `discover-acs`, on any feature the agent hasn't already worked this session.

**Skip when:** the agent just created the feature this session (context already warm). **Not for:** exploring whether a feature is worth doing (`discuss`).

## Workflow

1. **Resolve + locate** — resolve the methodology root + manifest via `${CLAUDE_PLUGIN_ROOT}/scripts/dae_resolve.py` (see `references/resolving.md`); locate the feature (slug arg or branch name). Reject if no folder / no `feature.md`.
2. **Silent batch load** — without narrating: `feature.md`, `CHARTER.md`, `manifest.yml`, prior `handoffs/` (especially the originating `*-discuss.md`), and the files named in `feature.md`'s "Related code / design pointers".
3. **Orient** — give a concise summary: outcome, scope, autonomy level (+ charter cap), key prior decisions, related code, relevant ADRs.
4. **One prompt** — ask exactly one question: anything else to load? If the user names a new code pointer, load it and offer to add it to `feature.md`. Then stop — prime-context orients, it does not interview.
5. **Handoff** — emit a summary.

Re-invocation re-loads fresh (no incremental diffing).

## Handoff

Emit per `${CLAUDE_PLUGIN_ROOT}/references/handoff-summary.md`. `checkpoint: null`; `artifacts: []`; `human_action_needed: no`; `recommended_next`: "/engineer.discover-acs".

## References

- [Foundation Design](https://www.notion.so/3585ecdee0e2811bbc67ff4913c03207) — feature.md schema
- [Discuss & Upstream Funnel](https://www.notion.so/35a5ecdee0e281eaa35fced0c4e23384) — methodology_root resolution

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.