skills.rest
8Dionysus
8DionysusCOMMUNITY
Explore all skills by this author →
GitHub

aoa-workspace-recon

Map AoA workspace ownership and supporting surfaces before cross-repo work.

2|Updated Mar 17, 2026
Search Tags:#provenance#agent orientation#workspace mapping#ownership boundaries#cross-repo change#local-first architecture
One-click install
npx skills add https://github.com/8Dionysus/8Dionysus --skill aoa-workspace-recon
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: aoa-workspace-recon
Source: https://github.com/8Dionysus/8Dionysus/tree/main/.codex/plugins/aoa-shared-launchers/skills/aoa-workspace-recon
Command: npx skills add https://github.com/8Dionysus/8Dionysus --skill aoa-workspace-recon

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires aoa_workspace, aoa_stats, dionysus.

What problem does it solve?

Prevents costly cross-repo mistakes by helping you quickly understand which AoA sibling workspace elements you own versus which you should treat as supporting surfaces during multi-repo tasks.

Core Features & Use Cases

  • Owning-repo identification: Produces a clear owning repo(s) map before you make changes.
  • Boundary warnings for shared surfaces: Flags misconceptions such as treating derived stats or root org surfaces as authority.
  • First bounded change recommendation: Suggests the smallest safe initial edit and a validation path to keep provenance legible.

Quick Start

Use aoa-workspace-recon to generate an ownership and boundary map for the AoA cross-repo task you are planning.

Frequently Asked Questions about aoa-workspace-recon

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I map ownership boundaries before making cross-repo changes?▼

Mapping ownership boundaries requires identifying owning repositories versus supporting surfaces before acting. This process clarifies provenance and flags shared surfaces, preventing you from treating derived stats or root org surfaces as authority during multi-repo work.

What's the best way to identify owning repos for AoA workspace tasks?▼

Identifying owning repos for AoA workspace tasks involves generating a structured map of workspace elements. This map distinguishes elements you own from supporting surfaces, providing boundary warnings and suggesting a smallest safe initial edit to keep changes bounded.

Why do I need workspace mapping for local-first architecture cross-repo work?▼

You need workspace mapping for local-first architecture cross-repo work because unclear ownership around shared surfaces causes costly mistakes. Mapping workspace-root configuration and sibling elements clarifies which surfaces you own versus support, ensuring provenance remains legible.

How do I find a safe first bounded change in a multi-repo workspace?▼

To find a safe first bounded change in a multi-repo workspace, generate an ownership and boundary map that suggests the smallest safe initial edit. This approach includes a validation path to ensure your cross-repo changes maintain clear provenance.

When should I treat derived stats or root org surfaces as supporting surfaces?▼

You should treat derived stats or root org surfaces as supporting surfaces, not authority, whenever they belong to non-owner repos in a cross-repo task. Boundary warnings flag these misconceptions to prevent unauthorized changes to shared surfaces.

Related Skills

Explore More Product & Management Skills→
HechaoYannetHechaoYannet

create-architecture

Generate a master architecture document from GDDs, ADRs, and governance constraints.

Community
Advanced
tonykooptonykoop

source-citations

Build and validate a centralized instrument-source registry with per-repo citations.

Community
Advanced
8Dionysus8Dionysus
2

aoa-growth-snapshot

Generate a bounded AoA growth snapshot from workspace, stats, and seed data.

Community
Intermediate
saranskumarsaranskumar

data-flow-designer

Document data sources, transformations, and sinks across multi-layer workflows.

Community
Intermediate