Skip to content

Huruikagi/pc-build-planner / .agents/skills/sb-configure

sb-configure

Verified

Configure or explicitly update SpecBind for a project and complete the resulting aftercare. Use for an explicit SpecBind binary or project-asset update request, initial post-install review, or later changes to Agents, role models, artifact language, project instructions, templates, shared Rules, operational adapters, Steering, or existing artifacts affected by configuration changes.

references/aftercare.md

View on GitHub
# Configuration aftercare

Run this phase after every successful configuration mutation.

## Re-establish current state

Run:

```sh
specbind configuration show
```

Then run the list, read, dry-run, parser, or status checks named by every
applicable configuration procedure. Judge from CLI output and repository state,
not from delegated narration.

## Classify follow-up

- **Required**: the configuration is invalid, a derived product asset has not
  been regenerated, or the requested surface is unusable without it. Complete
  this before reporting success.
- **Recommended**: consistency or the next ordinary workflow benefits from it,
  but current configuration remains valid. Perform it when already authorized;
  otherwise present it precisely.
- **Optional**: it changes additional artifacts, lifecycle evidence, durable
  knowledge, Git state beyond the active adapter-directed checkpoint, or an
  external system. Preview it and obtain its own choice.

Common mappings:

| Change | Follow-up |
| --- | --- |
| Agent or role | Reinstall and verify derived assets |
| Template | Offer existing-artifact reconciliation |
| Design candidate or selection | Inspect affected existing Specs |
| Rule | Offer review, never automatic rewrite |
| Steering | Check active-work assumptions |
| Adapter | Check the owning operational workflow |
| Language | Enumerate retained old-language project content, including `language-style` |
| Project instructions | Verify exact managed blocks and Skill discovery |

Declining optional follow-up completes the requested configuration change. Name
what remains and its effect without reporting it as a failure.

After required and authorized aftercare, read the Git adapter:

```sh
specbind adapter read git --for consume
```

Either `NO_CHANGE` result means there is no adapter-directed checkpoint.
Treat the configuration change as one eligible workflow unit: when the active
adapter requires a local checkpoint, stage only that unit and create it before
reporting completion. Never absorb unrelated changes or optional aftercare that
was declined.

## Separate authority boundaries

Do not infer authorization for existing-artifact mutation, lifecycle approval,
push, branch changes, tags, deployment, publication, destructive removal, or
history rewrite from the configuration request. The narrow local checkpoint
above is the only Git exception. Follow the owning workflow and its confirmation
boundary for each.
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: 472kUpdated Claude CodeCodexVerifiedInstall
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: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
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 availableStars: 322kUpdated Claude CodeCodexVerifiedInstall