swingerman/prime-context
engineer/skills/prime-context/SKILL.md
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".
$ install --global
skillsauthnpx skillsauth add swingerman/atdd prime-contextInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 5, 2026, 4:47 AM59.1s1 file scanned
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
- Resolve + locate — resolve the methodology root + manifest via
${CLAUDE_PLUGIN_ROOT}/scripts/dae_resolve.py(seereferences/resolving.md); locate the feature (slug arg or branch name). Reject if no folder / nofeature.md. - Silent batch load — without narrating:
feature.md,CHARTER.md,manifest.yml, priorhandoffs/(especially the originating*-discuss.md), and the files named infeature.md's "Related code / design pointers". - Orient — give a concise summary: outcome, scope, autonomy level (+ charter cap), key prior decisions, related code, relevant ADRs.
- 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. - Breadcrumb handoff — emit a tiny handoff recording what was loaded.
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".
Always emit a breadcrumb. Earlier versions produced no handoff because prime-context creates no artifact. Users expect a breadcrumb after every skill invocation (distbute Jun 4: "emit the handoff") — surprising them with "no artifact by design" breaks the agentic-summary contract. The breadcrumb records: which feature was primed, what files were loaded, any new pointer added to feature.md, and the next recommended skill. Body can be one paragraph — frontmatter is the load-bearing part for progress-log propagation.
References
- Foundation Design — feature.md schema
- Discuss & Upstream Funnel — methodology_root resolution
Related Skills
swingerman/post-merge
data-ai
VerifiedTrustedCommunity
Use immediately after a PR is merged to clean up the local feature branch and resync main. Triggers — "/engineer.post-merge", "did we merge", "did we push", "PR merged", "post-merge cleanup", or right after a `gh pr merge` succeeds in the same session.
103SKILL.mdUpdated Jun 5, 2026
swingerman/fix
data-ai
VerifiedTrustedCommunity
Use to drive a bug fix from first report through close, with a "why didn't we catch it?" loop at the end. Triggers — "/engineer.fix", "a bug came in", "this is broken", "a user reported X", "there's a defect", "we have a regression", "this needs a fix", "another report", "more issues", "still failing", "validation failed again", "another bug", "next defect", "more fixes".
103SKILL.mdUpdated May 26, 2026
swingerman/reorient
testing
VerifiedTrustedCommunity
Use mid-task when the working thread is lost — after a context compaction, a long agent run, or coming back to a feature unsure of the role, the current checkpoint, or the next action. Triggers — "/engineer.reorient", "reorient", "re-anchor", "what should I be doing right now", "I lost track", "where was I".
103SKILL.mdUpdated May 20, 2026
swingerman/arch-check
development
VerifiedTrustedCommunity
Use to check a feature's code against the charter's architecture rules — dependency layering, cycles, forbidden patterns, file naming, file size. Triggers — "/engineer.arch-check", "architecture check", "check architecture fitness", "does this follow the charter", "check layering".
103SKILL.mdUpdated May 19, 2026