workspace-autopsy-governance

Included with Lifetime

$97 forever

Conducts a full automated autopsy of the current workspace directory to map files, identifies structural issues, proposes a restructuring plan (the signal), and establishes unified governance using templates. Use this skill when a user asks to map, restructure, reorganize, or apply new governance to an existing messy repository.

Generalscriptsassets

What this skill does

# Workspace Autopsy & Governance Restructure

## Overview

This skill enables agents to systematically analyze (autopsy) an existing, potentially disorganized workspace, propose a logical new directory structure, and migrate the workspace to this new structure while enforcing new governance standards.

## Workflow

To execute this skill, follow these sequential steps:

### Phase 1: Workspace Autopsy (Mapping)
To begin, you must understand the current state of the workspace.
1. Run the autopsy script to map the directory:
`python /Users/4jp/.agents/skills/workspace-autopsy-governance/scripts/workspace_autopsy.py --dir .`
2. Review the generated map and statistics. Identify:
- Where the core source code lives.
- Where documentation, scripts, and assets are currently scattered.
- Legacy folders or structural chaos that need cleaning.

### Phase 2: Sending the Signal (Restructure Proposal)
Before moving any files, you must "send out the signal" to the user proposing the new structure and governance.
1. Read the template from `assets/RESTRUCTURE_PROPOSAL-template.md`.
2. Draft a customized `RESTRUCTURE_PROPOSAL.md` based on your findings from the autopsy. Detail exactly which directories will be created and which files will move where.
3. Present this proposal to the user and wait for their explicit approval. Do not proceed to Phase 3 without approval.

### Phase 3: Unite Under New Locations (Migration)
Once the user approves the proposal:
1. Create the new target directories (e.g., `/src`, `/docs`, `/scripts`, `/assets`, `/tests`) as agreed upon in the proposal.
2. Use standard shell commands (`mv`) to systematically migrate files from their old locations to the newly created, unified locations.
3. Ensure no orphaned files remain in chaotic root locations unless they are standard configuration files (e.g., `.gitignore`, `package.json`).

### Phase 4: Establish New Governance
With the files in their new locations, establish the rules that will govern them going forward.
1. Read the template from `assets/GEMINI-template.md`.
2. Customize it to reflect the specific standards, workflows, and constraints of the newly restructured project.
3. Write this customized governance document to `GEMINI.md` at the root of the project.
4. If appropriate, create subdirectory-specific `GEMINI.md` files for deeper governance (e.g., in `/src/GEMINI.md`).

## Resources Included

### `scripts/workspace_autopsy.py`
A Python script that traverses the specified directory, ignores common build/dependency folders, and prints a tree map along with statistics about file types and counts.

### `assets/RESTRUCTURE_PROPOSAL-template.md`
A template for the document you will generate to propose the new structure to the user.

### `assets/GEMINI-template.md`
A template for the governance rules to establish in the repository after the restructure.

Files: 7

Size: 10.4 KB

Complexity: 59/100

Category: General

Source: https://github.com/4444j99/a-i--skills/tree/main/distributions/claude/skills/workspace-autopsy-governance

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).

Generalscripts

relationship-science-coach

Included

Use this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.

Generalscripts

building-sf-integrations

Included

Salesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).

Generalscripts

venue-templates

Included

Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.

Generalscripts

let-fate-decide

Included

Draws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.

Generalscripts

net-ops

Included

Cross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.

Generalscripts