How do I install the Manifold Context skill?

Run npx skillmds@latest add tomevault-io/manifold-context in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Manifold Context safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Manifold Context?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Manifold Context free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Manifold Context?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Manifold Context by tomevault-io — Agent Skill

Name: Manifold Context
Author: tomevault-io

Manifold Context

Preserve Manifold constraint state for context retention. Reads .manifold/ directory and outputs a summary of current features, phases, constraints, tensions, and next actions. Use this skill when resuming work or before starting a new phase. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

/manifold-context

Purpose

Satisfies: RT-4 (Codex hooks via skills), TN1 (skills-as-hooks pattern)

This skill provides context preservation equivalent to Claude Code's PreCompact hook. Since Codex CLI does not have lifecycle hooks, this skill packages the same functionality as an on-demand capability.

When to Use

At the start of a session to load manifold context
Before starting a new manifold phase
When you need to recall the current state of constraint discovery
After context compression or token limits are approached

Instructions

Read all files in the .manifold/ directory of the current project. For each feature found:

Identify the feature from the filename (e.g., payment-retry.json → feature: payment-retry)
Read the JSON file (.manifold/<feature>.json) to get:
- Current phase (INITIALIZED, CONSTRAINED, TENSIONED, ANCHORED, GENERATED, VERIFIED)
- Constraint counts by category (business, technical, UX, security, operational)
- Tension count and resolution status
- Required truth statuses
- Convergence status
Read the MD file (.manifold/<feature>.md) to get:
- Outcome statement
- Key constraint statements
- Tension descriptions
Output a summary in this format:

## Manifold State

### Feature: <name>
- Phase: <phase> (<n>/6)
- Outcome: <outcome>
- Constraints: Business: <n>, Technical: <n>, UX: <n>, Security: <n>, Operational: <n>
- Tensions: <n> detected, <n> resolved
- Next: <suggested next command>

Phase → Next Action Mapping

Phase	Next Command
INITIALIZED	`/manifold:m1-constrain <feature>`
CONSTRAINED	`/manifold:m2-tension <feature>`
TENSIONED	`/manifold:m3-anchor <feature>`
ANCHORED	`/manifold:m4-generate <feature>`
GENERATED	`/manifold:m5-verify <feature>`
VERIFIED	Complete!

If no .manifold/ directory exists, output: "No manifold found in this project."

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: manifold-contextdescription: Preserve Manifold constraint state for context retention. Reads .manifold/ directory and outputs a summary of current features, phases, constraints, tensions, and next actions. Use this skill when resuming work or before starting a new phase. Use when this capability is needed.---# /manifold-context## PurposeSatisfies: RT-4 (Codex hooks via skills), TN1 (skills-as-hooks pattern)This skill provides context preservation equivalent to Claude Code's PreCompact hook.Since Codex CLI does not have lifecycle hooks, this skill packages the same functionalityas an on-demand capability.## When to Use- At the start of a session to load manifold context- Before starting a new manifold phase- When you need to recall the current state of constraint discovery- After context compression or token limits are approached## InstructionsRead all files in the `.manifold/` directory of the current project. For each feature found:1. **Identify the feature** from the filename (e.g., `payment-retry.json` → feature: `payment-retry`)2. **Read the JSON file** (`.manifold/<feature>.json`) to get: - Current phase (INITIALIZED, CONSTRAINED, TENSIONED, ANCHORED, GENERATED, VERIFIED) - Constraint counts by category (business, technical, UX, security, operational) - Tension count and resolution status - Required truth statuses - Convergence status3. **Read the MD file** (`.manifold/<feature>.md`) to get: - Outcome statement - Key constraint statements - Tension descriptions4. **Output a summary** in this format:```## Manifold State### Feature: <name>- Phase: <phase> (<n>/6)- Outcome: <outcome>- Constraints: Business: <n>, Technical: <n>, UX: <n>, Security: <n>, Operational: <n>- Tensions: <n> detected, <n> resolved- Next: <suggested next command>```### Phase → Next Action Mapping| Phase | Next Command ||-------|-------------|| INITIALIZED | `/manifold:m1-constrain <feature>` || CONSTRAINED | `/manifold:m2-tension <feature>` || TENSIONED | `/manifold:m3-anchor <feature>` || ANCHORED | `/manifold:m4-generate <feature>` || GENERATED | `/manifold:m5-verify <feature>` || VERIFIED | Complete! |If no `.manifold/` directory exists, output: "No manifold found in this project."---> Converted and distributed by [TomeVault](https://tomevault.io/claim/dhanesh) — claim your Tome and manage your conversions.

Frequently asked questions