원클릭으로 Manus에서 모든 스킬 실행

manifold-suggest

스타9

포크0

업데이트2026년 2월 12일 11:25

Analyze current tasks and suggest parallelization opportunities. Examines task descriptions for file overlap and dependency patterns to recommend safe parallel execution groups. Use when planning multi-task work.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

dhanesh

dhanesh/manifold

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

/manifold-suggest

Purpose

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

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

When to Use

When you have 2+ tasks that might be parallelizable
Before executing a multi-task plan from /manifold:m4-generate
When planning implementation of multiple artifacts

Instructions

When the user invokes this skill with a list of tasks (or you detect multiple tasks in the current plan):

Parse task descriptions to identify:
- Which files each task is likely to modify
- Dependencies between tasks (e.g., "implement auth" must precede "add auth tests")
- Estimated scope (single file, module, cross-cutting)
Detect file overlap between tasks:
- Tasks modifying the same files CANNOT run in parallel
- Tasks in different directories are usually safe to parallelize
- Test files can often run in parallel with implementation
Form safe parallel groups:
- Group tasks that have NO file overlap
- Identify sequential dependencies that must be preserved
- Calculate estimated speedup
Output a suggestion in this format:

## Parallelization Analysis

### Safe Parallel Groups
- **Group 1**: Task A, Task B (no file overlap)
- **Group 2**: Task C, Task D (independent modules)

### Sequential (must be ordered)
- Task E → Task F (dependency: E creates files F needs)

### Recommendation
<Parallelize / Sequential / Mixed> — Estimated speedup: <n>x

### Warnings
- <any overlap concerns or low-confidence predictions>

Decision Criteria

Condition	Recommendation
2+ tasks, no overlap	Parallelize
Some overlap, safe groups exist	Mixed (parallel groups + sequential)
All tasks overlap	Sequential
Single task	N/A

If the user hasn't specified tasks, check for a .manifold/ directory and look at the current phase to suggest what tasks might be parallelizable in the next phase.

이 저장소의 다른 Skills

같은 저장소

manifold-m3-anchor

dhanesh/manifold

Backward reasoning from desired outcome. Derives required conditions by asking 'What must be TRUE?'

2026-06-119

manifold-m5-verify

dhanesh/manifold

Verify ALL artifacts against ALL constraints. Produces a verification matrix showing coverage and gaps

2026-05-179

manifold-m-quick

dhanesh/manifold

Light mode: 3-phase workflow for simple changes. Use instead of full workflow for bug fixes, small features, or quick iterations.

2026-05-169

manifold-m-solve

dhanesh/manifold

Generate parallel execution plan from constraint network. Identifies waves, critical path, and bidirectional dependencies

2026-05-169

manifold-m0-init

dhanesh/manifold

Initialize a constraint manifold for a feature. Creates .manifold/<feature>.json + .manifold/<feature>.md

2026-05-169

manifold-m1-constrain

dhanesh/manifold

Interview-driven constraint discovery across 5 categories (business, technical, UX, security, operational)

2026-05-169

name	manifold-suggest
description	Analyze current tasks and suggest parallelization opportunities. Examines task descriptions for file overlap and dependency patterns to recommend safe parallel execution groups. Use when planning multi-task work.

/manifold-suggest

Purpose

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

When to Use

When you have 2+ tasks that might be parallelizable
Before executing a multi-task plan from /manifold:m4-generate
When planning implementation of multiple artifacts

Instructions

When the user invokes this skill with a list of tasks (or you detect multiple tasks in the current plan):

Parse task descriptions to identify:
- Which files each task is likely to modify
- Dependencies between tasks (e.g., "implement auth" must precede "add auth tests")
- Estimated scope (single file, module, cross-cutting)
Detect file overlap between tasks:
- Tasks modifying the same files CANNOT run in parallel
- Tasks in different directories are usually safe to parallelize
- Test files can often run in parallel with implementation
Form safe parallel groups:
- Group tasks that have NO file overlap
- Identify sequential dependencies that must be preserved
- Calculate estimated speedup
Output a suggestion in this format:

## Parallelization Analysis

### Safe Parallel Groups
- **Group 1**: Task A, Task B (no file overlap)
- **Group 2**: Task C, Task D (independent modules)

### Sequential (must be ordered)
- Task E → Task F (dependency: E creates files F needs)

### Recommendation
<Parallelize / Sequential / Mixed> — Estimated speedup: <n>x

### Warnings
- <any overlap concerns or low-confidence predictions>

Decision Criteria

Condition	Recommendation
2+ tasks, no overlap	Parallelize
Some overlap, safe groups exist	Mixed (parallel groups + sequential)
All tasks overlap	Sequential
Single task	N/A

If the user hasn't specified tasks, check for a .manifold/ directory and look at the current phase to suggest what tasks might be parallelizable in the next phase.