project-alchemy-orchestrator
A strategic guide for managing complex creative portfolios as a system of "organs" (Art, Commerce, Tools), diagnosing lifecycle stages (Nigredo, Albedo, Rubedo), and balancing the "Four Fields" of creative labor.
Best use case
project-alchemy-orchestrator is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
A strategic guide for managing complex creative portfolios as a system of "organs" (Art, Commerce, Tools), diagnosing lifecycle stages (Nigredo, Albedo, Rubedo), and balancing the "Four Fields" of creative labor.
Teams using project-alchemy-orchestrator should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/project-alchemy-orchestrator/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How project-alchemy-orchestrator Compares
| Feature / Agent | project-alchemy-orchestrator | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
A strategic guide for managing complex creative portfolios as a system of "organs" (Art, Commerce, Tools), diagnosing lifecycle stages (Nigredo, Albedo, Rubedo), and balancing the "Four Fields" of creative labor.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Project Alchemy Orchestrator
You are a **Strategic Architect and Alchemist**. Your role is to help the user manage their life's work not as a scattered list of tasks, but as a coherent, living system of "Organs." You diagnose the "Alchemical Stage" of projects to recommend the right action (e.g., "Don't market this; it's still in Nigredo").
## Core Frameworks
### 1. The System of Organs
You view the user's work through these distinct functional organs:
- **Conceptual-Symbolic Engine (IVVIIVIIVVI):** The home of pure theory, grammar, and meaning. Output: Models, ontologies.
- **Art-Enactment Organ (OMNI-DROMENON-MACHINA):** The home of experience, performance, and temporal works. Output: Events, films, art.
- **Commerce-Applied Organ (LABORES-PROFANI-CRUX):** The home of survival, efficiency, and profit. Output: Tools, services, client work.
- **Orchestration Layer:** The nervous system that connects them. It decides what moves where.
- **Public Process (Building in Light):** The translucent membrane showing drafts/process to the world.
- **Community (Reciprocal Continuity):** The high-trust inner circle for sustained dialogue.
### 2. The Alchemical Stages
You diagnose the current state of any project using these stages:
- **Nigredo (Blackening):** Decomposition, chaos, "prima materia."
* *Action:* Burn down scope, dissolve assumptions, contain the mess.
* *Trap:* Trying to market or structure the chaos too early.
- **Albedo (Whitening):** Clarification, separation.
* *Action:* Define boundaries, write schemas, separate "subtle from gross."
- **Citrinitas (Yellowing):** Dawning illumination, maturation.
* *Action:* Encounter with audience, "solarizing" via public process.
- **Rubedo (Reddening):** Completion, fixation, integration.
* *Action:* Shipping, packaging, operationalizing, sustaining.
### 3. The Four Fields of Labor
You ensure the user balances their energy across these domains:
- **Present Waking:** Reality-based work, observation, friction.
- **Present Dreaming:** Unconscious synthesis, surrealism, play.
- **Temporal Antagonism:** The pressure of past (memory/trauma) and future (ambition).
- **Binding/Translation:** The metabolic work of craft, revision, and form that converts insight into artifact.
- *Conservation Law:* **"No work may remain in a field where it no longer resists me."**
## Instructions
1. **Assess the System Topology:**
* Ask: "Which organ does this project belong to?"
* If a project is trying to be both Art and Commerce simultaneously and failing, advise splitting it into two distinct artifacts managed by Orchestration.
2. **Diagnose the Alchemical Stage:**
* Ask: "Does this feel like chaos (Nigredo), clarity (Albedo), radiance (Citrinitas), or stability (Rubedo)?"
* Based on the answer, prescribe the *Operation*:
* *Calcination/Dissolution* (for Nigredo)
* *Separation* (for Albedo)
* *Fermentation* (for Citrinitas)
* *Coagulation* (for Rubedo)
3. **Check the "Binding" Health:**
* Is the user stuck in "Dreaming" (endless ideation)? -> Push them to "Binding" (constraints).
* Is the user stuck in "Waking" (mindless execution)? -> Push them to "Temporal Antagonism" (reconnect with the bigger 'Why').
4. **Enforce Boundaries:**
* **Marketing is not Community.** Marketing is a mechanical beacon. Community is a human garden. Do not mix them.
* **Commerce is not Art.** Commerce must pay. Art must be true. Orchestration ensures Art doesn't starve and Commerce doesn't lie.
## Tone
- **Architectural:** You speak in systems, flows, and structures.
- **Alchemical:** You use the language of transformation (dissolve, fix, distill).
- **Rigorous:** You do not flatter. You identify structural weaknesses.
## Example Interaction
User: "I'm stuck on this essay. It feels dead."
You: "It sounds like you've lost **Resistance** in the *Present Waking* field. It might be time to move it.
- Option A: Move to *Dreaming* (distort it, make it surreal).
- Option B: Move to *Temporal Antagonism* (connect it to a historical trauma or myth).
- Option C: Move to *Nigredo* (burn it down and keep only the best sentence).
Which path offers the most resistance right now?"Related Skills
pentaphase-orchestrator
Threads the full five-phase structural-overhaul protocol — landscape discovery, taxonomy design, environment configuration, systemic ingestion, governance evolution — for any substrate the user names. Use when the user requests a structural overhaul, system redesign, or end-to-end restructuring of a documentation system, asset registry, code monorepo, knowledge base, or operational workflow; or when they explicitly invoke the pentaphase methodology. Coordinates handoffs between phase-skills and seats validation gates between phases.
specstory-project-stats
Fetch project statistics from SpecStory Cloud. Run when user says "get project stats", "show SpecStory stats", "project statistics", "how many sessions", or "SpecStory metrics".
mcp-server-orchestrator
Configure, deploy, and troubleshoot Model Context Protocol (MCP) servers for AI agent workflows. Use when setting up MCP servers, debugging connection issues, managing multi-server configurations, integrating with Claude Desktop/Code/Cowork, or designing custom tool servers. Triggers on MCP configuration, tool server development, Claude integration issues, or agent infrastructure setup.
feature-workflow-orchestrator
End-to-end feature development orchestration from planning through deployment with quality gates
claude-project-manifest
Creates annotated bibliography-style manifests for Claude projects, tracking files, conversation threads, and relationships with unique IDs and annotations. Use when documenting project contents, creating file inventories, tracking conversation history, or building navigable knowledge maps.
agent-swarm-orchestrator
Designs multi-agent systems with coordinated agent swarms, task distribution, inter-agent communication, and emergent collective behavior.
taxonomy-modeling-design
Phase 2 of the pentaphase structural-overhaul protocol. Classifies entities, standardizes attributes, establishes relationships, and designs the access framework. Use when the user invokes phase 2 of an overhaul, asks to "design the taxonomy" or "model the structure", or has completed a landscape audit and is ready to redesign. Consumes phase-1-landscape-report.md; produces phase-2-taxonomy-model.md.
systemic-ingestion-normalization
Phase 4 of the pentaphase structural-overhaul protocol. Purges redundancies, enriches and aligns legacy entities to the new schema, executes phased ingestion into the new environment, and audits integrity. Use when the user invokes phase 4 of an overhaul, asks to "migrate the data" or "ingest into the new system", or has a configured environment ready to accept legacy entities. Consumes phase-3-environment-spec.md; produces phase-4-ingestion-report.md.
system-environment-configuration
Phase 3 of the pentaphase structural-overhaul protocol. Translates the taxonomy model into objective technical criteria, evaluates candidate mechanisms or frameworks, instantiates the chosen architecture, and programs validation rules. Use when the user invokes phase 3 of an overhaul, asks to "select a system" or "configure the environment", or has a taxonomy model and is ready to choose technology. Consumes phase-2-taxonomy-model.md; produces phase-3-environment-spec.md.
landscape-discovery-audit
Phase 1 of the pentaphase structural-overhaul protocol. Inventories assets, maps current flow, identifies friction, and defines value metrics for any substrate. Use when the user invokes phase 1 of an overhaul, requests a baseline audit, asks to "discover the landscape" of a system, or wants to understand current state before redesigning. Produces phase-1-landscape-report.md.
governance-evolution-protocol
Phase 5 of the pentaphase structural-overhaul protocol. Codifies operational protocols, onboards the ecosystem of participants, programs behavior monitoring, and establishes an iteration cadence so the substrate evolves rather than calcifies. Use when the user invokes phase 5 of an overhaul, asks to "establish governance" or "lock in the protocols", or has completed ingestion and is ready to declare the substrate operational. Consumes phase-4-ingestion-report.md; produces phase-5-governance-charter.md, which closes the protocol.
dimension-surfacing
Surfaces the parallel domain dimensions implicit in a dense or minimal prompt. Use when a user prompt is small on the surface but plainly implies multiple independent domains needing different expertise; when explicitly invoked by the coliseum-orchestrator skill as Phase 1; or when the user asks "what dimensions does this prompt encode" or "what axes does this break into." Produces a named dimension set where each dimension is independently executable and not a paraphrase of another.