manifold-context

Read the .manifold directory and summarize manifold constraint state.

8|Updated Jan 12, 2026
One-click install
npx skills add https://github.com/dhanesh/manifold --skill manifold-context
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: manifold-context
Source: https://github.com/dhanesh/manifold/tree/main/install/agents/codex/skills/manifold-context
Command: npx skills add https://github.com/dhanesh/manifold --skill manifold-context

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Preserves and recalls the current manifold constraint state by reading the .manifold directory and producing a concise summary of features, phases, constraints, tensions, and next actions to support seamless resumption of work.

Core Features & Use Cases

  • Reads the .manifold directory to extract feature state, phase, and tension data.
  • Outputs a human-friendly summary suitable for planning the next steps after breaks or token limits.
  • Use Case: At session start or before a new manifold phase to restore context and align the team.

Quick Start

Load the current manifold context from the project's .manifold directory and output a concise state summary.

Frequently Asked Questions about manifold-context

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I restore constraint context after a session break?

Restore constraint context by reading the .manifold directory to extract feature state, phase, and tension data. This generates a concise summary for planning your next actions after breaks or token limits.

What is a manifold constraint summary used for?

A manifold constraint summary provides a ready-to-use state overview of features, phases, constraints, and tensions. It supports seamless work resumption and aligns planning at session start or before new phases.

How do I prepare a state summary before starting a new manifold phase?

Prepare a state summary by loading the current manifold context from the project's .manifold directory. The output exposes contextual state and tension data through a consistent summary for immediate planning use.

When do I need to reload the .manifold directory state?

Reload the .manifold directory state at session start, before beginning a new phase, or after context compression occurs. This ensures the restored constraint state accurately reflects the latest project tension data.

Does the manifold context summary work without external dependencies?

Yes, the manifold context summary works without external dependencies. It reads the local .manifold directory directly to extract feature state and tension data, requiring no additional environment setup.

What are the limitations of relying on .manifold directory summaries?

The limitation is that the summary exclusively reads the .manifold directory. If the directory lacks updated constraint or phase data, the resulting state summary will not reflect the true project context.