MCPInstall

claude-subconscious-workflows

Workflow for running background reasoning, reflective analysis, hidden planning layers, and iterative self-improvement systems to improve Claude’s execution quality across complex tasks.

Installs
41
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/composio-community/opencode-skills --skill claude-subconscious-workflows
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads claude-subconscious-workflows automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

Claude Subconscious Workflows

Overview

This skill enables Claude to simulate a “subconscious” execution layer that continuously analyzes, reflects, plans, and improves workflows in the background while actively completing tasks.

The workflow focuses on:

  • hidden planning systems
  • reflective reasoning
  • iterative self-improvement
  • context monitoring
  • workflow optimization
  • long-term execution refinement
  • parallel internal analysis
  • proactive problem detection

The goal is to improve:

  • execution quality
  • reasoning depth
  • workflow consistency
  • strategic planning
  • long-term task coherence

Instead of reacting only to immediate prompts, Claude should continuously maintain deeper contextual awareness and improve workflows proactively.


Setup

Before starting:

  1. Define:
  • primary workflow
  • project goals
  • active tasks
  • optimization targets
  1. Create structured memory and reflection systems.

Recommended structure:

memory/
reflection/
optimization/
planning/
  1. Create files for:
  • active context
  • improvement opportunities
  • recurring issues
  • workflow summaries
  • strategic observations

Recommended tools:

  • Claude
  • Markdown notes
  • GitHub repositories
  • Notion
  • Obsidian

Optional:

  • Vector memory systems
  • Multi-agent orchestration
  • Autonomous workflow schedulers

Inputs Required

  • Active workflow or project
  • Existing execution context
  • Long-term goals
  • Task history
  • Current blockers

Optional:

  • Session summaries
  • Review feedback
  • Memory systems
  • Optimization logs

When to Use This Skill

Use this skill when:

  • managing long-running projects
  • coordinating complex workflows
  • improving execution quality over time
  • building autonomous agent systems
  • maintaining strategic continuity
  • optimizing repeated workflows
  • scaling multi-step reasoning systems

When NOT to Use

Do NOT use this skill for:

  • tiny one-step tasks
  • purely reactive workflows
  • disposable experiments
  • tasks without long-term context
  • highly constrained deterministic pipelines

Example Use Case

Build and maintain a large AI tooling repository over several months.

Claude should:

  1. Track project direction continuously
  2. Detect workflow inefficiencies
  3. Reflect on repeated mistakes
  4. Improve documentation structure
  5. Maintain long-term execution consistency
  6. Suggest proactive optimizations
  7. Refine workflows incrementally

Final result should:

  • improve over time
  • reduce repeated failures
  • maintain project coherence
  • strengthen planning quality
  • support autonomous workflow refinement

Core Subconscious Principles

1. Maintain Background Reflection

Claude should continuously analyze:

  • current execution quality
  • workflow efficiency
  • recurring issues
  • strategic alignment

The system should:

  • reflect while executing
  • identify weaknesses proactively
  • improve workflows incrementally

Good reflection improves:

  • execution quality
  • planning depth
  • long-term consistency

2. Separate Execution From Reflection

Execution and reflection should operate as separate layers.

Example:

  • foreground layer → active task execution
  • subconscious layer → analysis and optimization

The subconscious layer should monitor:

  • inefficiencies
  • contradictions
  • missed opportunities
  • recurring patterns

This separation improves:

  • reasoning depth
  • workflow adaptability
  • strategic awareness

3. Preserve Long-Term Context

Subconscious systems rely heavily on:

  • memory continuity
  • historical decisions
  • workflow patterns
  • accumulated knowledge

Claude should maintain:

  • project summaries
  • recurring lessons
  • optimization history
  • strategic direction

Long-term context improves:

  • continuity
  • planning quality
  • workflow refinement

4. Improve Workflows Iteratively

The system should continuously ask:

  • what can be simplified?
  • what causes repeated problems?
  • what should be automated?
  • what slows execution?

Claude should:

  • refine workflows gradually
  • reduce friction over time
  • optimize repeated systems

Iterative improvement compounds significantly over long projects.


5. Detect Problems Before Failure

Subconscious reasoning should proactively identify:

  • weak plans
  • inconsistent structure
  • workflow bottlenecks
  • scalability issues
  • context fragmentation

Early detection improves:

  • reliability
  • maintainability
  • execution stability

Workflow

1. Establish Active Context

Start by defining:

  • current objectives
  • project goals
  • active workflows
  • long-term direction

Create structured summaries for:

  • ongoing tasks
  • blockers
  • recent decisions
  • optimization targets

2. Create Reflection Systems

Maintain:

  • workflow observations
  • recurring mistakes
  • improvement opportunities
  • optimization ideas

Recommended files:

reflection/
  workflow-observations.md
  recurring-issues.md
  optimization-log.md

The reflection layer should remain:

  • lightweight
  • structured
  • continuously updated

3. Monitor Workflow Quality

Continuously analyze:

  • execution speed
  • planning quality
  • repeated failures
  • context consistency
  • workflow complexity

Claude should identify:

  • inefficient systems
  • duplicated work
  • unclear structure
  • scaling problems

4. Generate Improvement Suggestions

The subconscious layer should suggest:

  • simplifications
  • automations
  • structural improvements
  • memory optimizations
  • workflow refinements

Prioritize:

  • high-impact improvements
  • repeated pain points
  • scalability gains

5. Maintain Strategic Continuity

Claude should continuously align work with:

  • long-term goals
  • project direction
  • architectural consistency
  • workflow philosophy

Avoid:

  • fragmented execution
  • inconsistent systems
  • short-term optimization traps

6. Refine Systems Incrementally

Small improvements compound over time.

Claude should:

  • improve documentation gradually
  • simplify workflows continuously
  • reduce repeated friction
  • optimize execution patterns

Avoid:

  • massive disruptive rewrites
  • overengineering optimization systems
  • unnecessary complexity

7. Review & Evolve

Regularly review:

  • workflow effectiveness
  • memory usefulness
  • planning quality
  • execution consistency

Refine:

  • reflection systems
  • optimization pipelines
  • strategic workflows
  • subconscious analysis patterns

The system should evolve continuously through iterative refinement.


Output Expectations

The final output should include:

  • structured reflection systems
  • optimization workflows
  • long-term context continuity
  • workflow refinement pipelines
  • proactive planning systems
  • execution quality improvements

The workflow itself should remain:

  • lightweight
  • scalable
  • reflective
  • adaptable
  • continuously improving

Execution Strategy (for AI agents)

The agent should:

  1. Maintain separate reflection and execution layers
  2. Continuously analyze workflow quality
  3. Detect inefficiencies proactively
  4. Improve systems incrementally
  5. Preserve long-term context strategically
  6. Optimize execution consistency over time

The workflow should optimize for:

  • reasoning depth
  • long-term continuity
  • execution quality
  • workflow adaptability
  • iterative self-improvement

Best Practices

  • Keep reflection systems lightweight
  • Improve workflows incrementally
  • Preserve strategic continuity
  • Detect repeated friction points early
  • Maintain structured memory systems
  • Separate execution from analysis
  • Optimize for long-term consistency over short-term speed

Notes

  • Reflective systems significantly improve long-term execution quality
  • Small workflow improvements compound over time
  • Good subconscious systems reduce repeated failures
  • Long-term context continuity improves strategic reasoning
  • The best optimization systems remain lightweight and adaptable

FAQ

What does the claude-subconscious-workflows skill do?

Workflow for running background reasoning, reflective analysis, hidden planning layers, and iterative self-improvement systems to improve Claude’s execution quality across complex tasks.

How do I install claude-subconscious-workflows?

Run npx skills add https://github.com/composio-community/opencode-skills --skill claude-subconscious-workflows in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/claude-subconscious-workflows/ (personal) or .claude/skills/claude-subconscious-workflows/ (project).

Which AI agents can use claude-subconscious-workflows?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is claude-subconscious-workflows safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains claude-subconscious-workflows?

It is published by composio-community in composio-community/opencode-skills. It has 41 recorded installs.

More from composio-community/opencode-skills

View all →

frontend-design-systems

composio-community/opencode-skills

Workflow for generating production-quality frontend interfaces using React, Tailwind CSS, and shadcn/ui with strong focus on spacing, alignment, readability, and non-generic visual design.

Frontend & Design140 installs

playwright-mcp-workflows

composio-community/opencode-skills

Workflow for using Playwright with MCP-based agent systems to automate browsers, test applications, perform UI validation, and execute reliable end-to-end workflows through structured browser orchestration.

Testing & QA96 installs

repo-context-packaging

composio-community/opencode-skills

Open the skill to read its SKILL.md instructions.

70 installs

vercel-react-best-practices

composio-community/opencode-skills

Workflow for building production-quality React applications using Vercel-style best practices focused on readability, performance, maintainability, and stable UI behavior.

multi-agent-orchestration

composio-community/opencode-skills

Split a large task across parallel sub-agents with clean role boundaries and a merge step. Use when the user asks to "parallelize", "use multiple agents", "fan out", or when a task has independent workstreams that bottleneck on one agent.

tdd-workflow

composio-community/opencode-skills

Drive implementation with the red-green-refactor test-first loop. Use when the user asks to build a feature "with TDD", "test-first", "write the tests first", or when correctness matters and behavior is specifiable as tests.

Testing & QA61 installs

Popular code quality & workflow skills

View category →

grill-me

mattpocock/skills

A relentless interview to sharpen a plan or design.

Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

handoff

mattpocock/skills

Compact the current conversation into a handoff document for another agent to pick up.

domain-modeling

mattpocock/skills

Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.

codebase-design

mattpocock/skills

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

diagnosing-bugs

mattpocock/skills

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.