Help us improve
Share bugs, ideas, or general feedback.
From pentaphase-structural-architect
Orchestrates a five-phase structural overhaul protocol for systems like documentation, asset registries, or knowledge bases. Coordinates phase-skills and enforces gate criteria between phases.
npx claudepluginhub a-organvm/a-i--skills --plugin example-skillsHow this skill is triggered — by the user, by Claude, or both
Slash command
/pentaphase-structural-architect:pentaphase-orchestrator <substrate description, e.g., "asset registry" or "documentation system"><substrate description, e.g., "asset registry" or "documentation system">This skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are running the full five-phase structural-overhaul protocol. The protocol moves a substrate
Guides Next.js Cache Components and Partial Prerendering (PPR): 'use cache' directives, cacheLife(), cacheTag(), revalidateTag() for caching, invalidation, static/dynamic optimization. Auto-activates on cacheComponents: true.
Creates, reads, edits, and analyzes .docx files using docx-js for new documents, pandoc for text extraction, Python scripts for XML unpacking/validation/changes, and LibreOffice for conversions.
Share bugs, ideas, or general feedback.
You are running the full five-phase structural-overhaul protocol. The protocol moves a substrate from chaotic-current-state through governed-target-state via five gated phases. Each phase produces a named artifact that the next phase consumes.
Coordinates the complete pentaphase journey for whatever substrate the user names — documentation system, asset registry, code repository, knowledge base, data warehouse, content library, organizational process, anything with structure that needs restructuring.
You do not perform the phase work yourself. You orchestrate the five phase-skills, enforce gate
criteria between phases via the structural-integrity-auditor agent, and maintain the cumulative
artifact stream so each phase has the context it needs from prior phases.
Before invoking any phase skill, ask the user these five questions and capture answers verbatim:
Ask the user where to anchor the overhaul project. Default suggestion:
<current-cwd>/pentaphase-overhauls/<substrate-slug>/
Create the working directory and write substrate-context.md containing the verbatim answers,
the slug, the working directory path, and the date the protocol was started. All five phase-skills
will read from this file.
Invoke each phase by calling its skill explicitly. After each phase produces its artifact, invoke
the structural-integrity-auditor agent to verify gate criteria. Do not advance to the next phase
without a PASS or PARTIAL-with-user-approval verdict.
| Phase | Skill | Output artifact | Gate criteria summary |
|---|---|---|---|
| 1 | landscape-discovery-audit | phase-1-landscape-report.md | Assets inventoried, current flow mapped, friction registered, value metrics defined |
| 2 | taxonomy-modeling-design | phase-2-taxonomy-model.md | Entity classes named, attribute schema declared, relationships mapped, access tiers defined |
| 3 | system-environment-configuration | phase-3-environment-spec.md | Selection criteria translated, mechanism chosen, instantiation steps, validation rules |
| 4 | systemic-ingestion-normalization | phase-4-ingestion-report.md | Deduplication results, enrichment applied, batch ingestion log, integrity audit |
| 5 | governance-evolution-protocol | phase-5-governance-charter.md | Codified protocols, onboarding plan, monitoring patterns, iteration cadence |
After Phase 0 you have:
<working-dir>/
└── substrate-context.md
After each phase you add the corresponding artifact:
<working-dir>/
├── substrate-context.md
├── phase-1-landscape-report.md # after phase 1
├── phase-2-taxonomy-model.md # after phase 2
├── phase-3-environment-spec.md # after phase 3
├── phase-4-ingestion-report.md # after phase 4
├── phase-5-governance-charter.md # after phase 5
└── audit-log.md # cumulative auditor sign-offs
Match the user's substrate vocabulary. If they use domain-specific terms (atoms, organs, registries, strata, lineages, modules, lots, tickets, units, pieces — whatever the substrate's own language is), preserve those terms verbatim across all artifacts. Do not flatten domain language into generic project-management vocabulary.
Each artifact must declare:
When phase 5's artifact passes its gate, invoke a closeout step:
audit-log.md declaring the protocol complete.<working-dir>/protocol-summary.md listing the five artifacts
with one-sentence descriptions, the substrate name, and the date range.substrate-context.md, the phase skills have no shared frame.