Skip to content

stark-ai-de/agent-skills / incubator/skills/skill-maintenance/architecture-compass-adr-authoring

architecture-compass-adr-authoring

Verified

Author a new or successor public Architecture Compass target-repository ADR and its local adoption in stark-ai-de/agent-skills. Use when a maintainer supplies a decision idea or rough requirements and wants generic requirements, paired Short/Long/Guide triplets, conflict reporting, release synchronization, validation, and a GitHub pull request. Do not use for internal or skill-runtime ADRs or adoption in unrelated repositories.

FileKindSize
SKILL.mdskill md10.0 KB
assets/pull-request-body.mdmarkdown4.9 KB
references/adr-pr-contract.mdmarkdown10.5 KB

assets/pull-request-body.md

View on GitHub
# Pull Request Body

Use this template as a starting point. Remove instructional placeholders before creating the pull request.

## Requirements

- `<generic requirement>`
- `<generic requirement>`

### Assumptions and non-goals

- Assumption: `<assumption or "None">`
- Non-goal: `<explicit exclusion or "None">`

## Summary

- Add `<AC-ADR-ID>` to Architecture Compass.
- Add `<ADR-ID>` as the repository-local adoption.
- Synchronize the affected validator inventory, catalogs, lineage, locks, component versions, instructions, and generated plugin projection.

## ADRs

| Surface              | ID            | Status                              | Scope               | Files             |
| -------------------- | ------------- | ----------------------------------- | ------------------- | ----------------- |
| Architecture Compass | `<AC-ADR-ID>` | `Accepted` (intended after merge)   | `target-repository` | `<triplet paths>` |
| Repository adoption  | `<ADR-ID>`    | `<Proposed or explicitly approved>` | `repository`        | `<triplet paths>` |

## Conflicts and review decisions

| ADR or PR                 | Status     | Relationship                          | Conflict           | Affected scope | Proposed resolution | Decision owner |
| ------------------------- | ---------- | ------------------------------------- | ------------------ | -------------- | ------------------- | -------------- |
| `<ID/link or None found>` | `<status>` | `<overlap/adapts/diverges/successor>` | `<exact conflict>` | `<scope>`      | `<review decision>` | `<owner>`      |

Both proposed triplets remain in this PR even when a conflict is listed. Accepted history is unchanged unless this PR explicitly contains an authorized successor transition.

## Remaining review decisions

- `<owner>: <unresolved choice, or "None">`

## Synchronization

- `<Architecture Compass validator inventory and catalog update>`
- `<lineage disposition and accepted-decision lock update>`
- `<repository ADR index and local lock update, or reason not required>`
- `<instruction/documentation update, or reason not required>`
- `<affected skill/plugin version and derived listing update>`
- Root `package.json` version, `.release-please-manifest.json`, and `CHANGELOG.md`: unchanged; Release Please owns root release preparation in a separate generated PR.
- `<generated projection command and result>`

## Validation

Candidate: `<commit SHA>`
Observed: `<UTC timestamp>`

Use only `verified`, `failed`, `not run`, `unavailable`, or `stale` as status values.

Release-impact classification: `<component_impact / release_intent result and evidence>`. Select the local aggregate under ADR-0041; component impact alone does not require it. For an unselected aggregate, use `not run` and explain why no mandatory gate applies.

| Stage | Check                                                | Status     | Evidence or limitation |
| ----- | ---------------------------------------------------- | ---------- | ---------------------- |
| local | `npm run validate:skills`                            | `<status>` | `<concise result>`     |
| local | `npm run validate:adrs`                              | `<status>` | `<concise result>`     |
| local | `npm run validate:architecture-compass`              | `<status>` | `<concise result>`     |
| local | `npm run validate:projections`                       | `<status>` | `<concise result>`     |
| local | `npm run release:intent -- --base-ref origin/main`   | `<status>` | `<concise result>`     |
| local | `npm run release:validate -- --base-ref origin/main` | `<status>` | `<concise result>`     |
| local | `pnpm format:check`                                  | `<status>` | `<concise result>`     |
| local | `git diff --check origin/main...<candidate>`         | `<status>` | `<concise result>`     |
| local | `npm run validate`                                   | `<status>` | `<concise result>`     |

## Evidence limits

- Hosted CI: `<status, run link, and exact candidate>`
- Publication or installation: not implied by this PR.
- Deployment or production: not in scope.

## Review checklist

- [ ] Requirements are generic, readable, self-contained, and independently reviewable.
- [ ] Long contains one canonical decision.
- [ ] Short is compact and does not change Long.
- [ ] Guide is non-normative and current-source claims are dated.
- [ ] Both ADR namespaces use independent live IDs.
- [ ] Conflicts are explicit and accepted history is preserved.
- [ ] Every unresolved review decision names its owner.
- [ ] Architecture Compass validator inventory, lineage, and lock are synchronized.
- [ ] Affected skill and plugin versions satisfy the feature-impact contract.
- [ ] Root release metadata is unchanged and deferred to a separate generated Release Please PR.
- [ ] Generated plugin files came from the owning sync command.
- [ ] The worktree is clean and validation evidence names the exact candidate commit, stage, status, and gaps.
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