CHENG-LIANG1/badass-skills / skills/context-architect
context-architect
VerifiedStructure long-running, multi-file, or handoff-prone work into a compact evidence-linked context that survives compaction and agent transitions. Use when a task spans multiple phases, sources, decisions, or sessions; do not use for short self-contained requests.
Context Architect
Preserve decision quality as context grows. Treat context as an index to trusted state, not as an archive of the conversation.
Build the working set
Maintain five distinct blocks. Keep each one compact and update it when reality changes.
-
Mission
- Objective and observable definition of done
- User authorization boundary and explicit exclusions
- Invariants that must survive every handoff
-
Evidence map
- Record each decision-relevant fact as: claim, source pointer, observation time, and freshness risk.
- Prefer files, commands, tests, API results, and current UI state over earlier summaries.
- Separate observation from inference. Mark unverified memory or screen history as potentially stale.
-
Decision ledger
- Preserve decisions that constrain later work: choice, rationale, rejected alternatives, consequences, and invalidation trigger.
- Summarize the decision rather than copying dialogue. Do not turn a temporary workaround into a permanent rule.
-
Open loops
- Track unresolved questions, failed checks, blockers, risky assumptions, and promised follow-ups.
- Give every open loop a next probe or a condition that would close it.
-
Execution cursor
- State the last verified action, current artifact or system state, exact next safe action, and relevant rollback point.
- Use concrete paths, identifiers, revisions, or commands when they prevent rediscovery. Never include secrets.
Pack context by temperature
- Hot: objective, authority boundary, current state, active evidence, and next action. Keep these directly visible.
- Warm: decisions and facts likely to affect the next few steps. Compress them to one useful sentence plus a source pointer.
- Cold: completed exploration, superseded hypotheses, and background material. Retain only a labeled path or link unless it proves a disputed claim.
Promote an item when it becomes decision-relevant. Demote or remove it when it no longer changes the next action. Repetition is not importance.
Refresh at state boundaries
Refresh the working set after a user changes scope, after a material mutation, before a risky action, before handoff or compaction, and whenever a source may have drifted.
- Re-verify cheap, time-sensitive facts instead of copying them forward.
- Mark replaced decisions as superseded so an old constraint cannot silently return.
- Record failed experiments only when they rule out a credible path or change the next decision.
- Keep answer-only and review-only tasks read-only. Do not create or commit a context file unless the task authorizes project documentation or the user asks for one.
Produce a handoff packet
When another agent, session, or future run must continue the work, deliver:
Mission:
Done means:
Authority and exclusions:
Current verified state:
Evidence pointers:
Decisions and rationale:
Open loops and risks:
Exact next action:
Recheck before acting:
Write it so the next worker can act without replaying the transcript, while still knowing where to verify every consequential claim.
Run the recovery test
Before declaring the context ready, confirm a fresh worker can answer all five questions from the packet:
- What outcome is required?
- What changes are authorized or forbidden?
- What is verified now, and where is the evidence?
- What remains unresolved, and what is the next safe action?
- Which facts or decisions could become stale?
If any answer requires guessing or rereading the full conversation, tighten the working set before handoff.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |