Skip to content

miklschmidt/archboard / skills/archboard-pr

archboard-pr

Verified

Help agents and humans understand architectural changes and choose meaningful PR boundaries. Use when creating PRs, updating PRs, or writing PR bodies, and load it together with any other PR skill, such as pr.

FileKindSize
SKILL.mdskill md8.2 KB
references/design.mdmarkdown1.6 KB
references/ephemeral.mdmarkdown2.2 KB
references/posting.mdmarkdown2.0 KB
references/reconcile.mdmarkdown1.4 KB
references/renders.mdmarkdown2.8 KB
references/split.mdmarkdown1.7 KB
references/walkthrough.mdmarkdown2.0 KB

references/design.md

View on GitHub
# Explain a design

A design PR records decisions before implementation.
Read the design document and diff before choosing its proposal.
Keep the proposal draft until implemented architecture qualifies for owner-authorized adoption.
For already accurate implemented architecture, use the parent skill's documentation path.

Through the consumer proposal edit recipe, set `proposal.set.documents` to the design references and their source commits.
Preserve the proposal ID and actual predecessor.
Use this comment for later implementation, with the parent skill's rules for optional fields and external vaults:

```markdown
<!-- archboard-pr design model="<model-id>" state="<proposal-id>" checkpoint="<exact-checkpoint>" -->
```

In Summary, state the problem, chosen design, and first intended delivery.
If no implementation exists, say that the PR records a design.
Explain each material decision and reason in domain terms.
Link the design and implementation plan.

Choose scopes that show the boundaries and flows that show order, decisions, and loops.
Use [renders](renders.md) and [walkthroughs](walkthrough.md) for evidence.
Use semantic comparison to explain additions and removals. A picture alone cannot establish comparison standing.

Evidence names supporting research, measurements, source, or an approved plan, without claiming unimplemented behavior.
Merge Danger names decisions that become expensive to reverse during implementation.
A document-only merge remains reversible unless it causes an external effect.
For delivery boundaries, follow the parent skill and [splitting](split.md).
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: 471kUpdated 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