Project Planner
adrianpuiu/claude-skills-marketplace
Comprehensive project planning and documentation generator for software projects.
Evaluate-Loop Step 1: PLAN. An agent skill from Ibrahim-3d/orchestrator-supaconductor.
$ npx skills add Ibrahim-3d/orchestrator-supaconductor --skill loop-planner -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Ibrahim-3d/orchestrator-supaconductor loop-planner --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Ibrahim-3d/orchestrator-supaconductor.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/loop-planner .claude/skills/loop-planner && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "loop-planner" agent skill from https://github.com/Ibrahim-3d/orchestrator-supaconductor/tree/master/skills/loop-planner into .claude/skills/loop-planner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "loop-planner", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Ibrahim-3d/orchestrator-supaconductor/tree/master/skills/loop-plannerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Ibrahim-3d/orchestrator-supaconductor --skill loop-planner -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Ibrahim-3d/orchestrator-supaconductor loop-planner --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Ibrahim-3d/orchestrator-supaconductor.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/loop-planner .agents/skills/loop-planner && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "loop-planner" agent skill from https://github.com/Ibrahim-3d/orchestrator-supaconductor/tree/master/skills/loop-planner into .agents/skills/loop-planner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "loop-planner", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Ibrahim-3d/orchestrator-supaconductor --skill loop-planner -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Ibrahim-3d/orchestrator-supaconductor loop-planner --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Ibrahim-3d/orchestrator-supaconductor.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/loop-planner .cursor/skills/loop-planner && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "loop-planner" agent skill from https://github.com/Ibrahim-3d/orchestrator-supaconductor/tree/master/skills/loop-planner into .cursor/skills/loop-planner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "loop-planner", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Ibrahim-3d/orchestrator-supaconductor.git --path skills/loop-planner--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Ibrahim-3d/orchestrator-supaconductor --skill loop-planner -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Ibrahim-3d/orchestrator-supaconductor loop-planner --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Ibrahim-3d/orchestrator-supaconductor.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/loop-planner .gemini/skills/loop-planner && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "loop-planner" agent skill from https://github.com/Ibrahim-3d/orchestrator-supaconductor/tree/master/skills/loop-planner into .gemini/skills/loop-planner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "loop-planner", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Ibrahim-3d/orchestrator-supaconductor loop-plannerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Ibrahim-3d/orchestrator-supaconductor --skill loop-planner -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Ibrahim-3d/orchestrator-supaconductor.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/loop-planner .github/skills/loop-planner && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "loop-planner" agent skill from https://github.com/Ibrahim-3d/orchestrator-supaconductor/tree/master/skills/loop-planner into .github/skills/loop-planner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "loop-planner", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Ibrahim-3d/orchestrator-supaconductor --skill loop-planner -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Ibrahim-3d/orchestrator-supaconductor loop-planner --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Ibrahim-3d/orchestrator-supaconductor.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/loop-planner .opencode/skills/loop-planner && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "loop-planner" agent skill from https://github.com/Ibrahim-3d/orchestrator-supaconductor/tree/master/skills/loop-planner into .opencode/skills/loop-planner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "loop-planner", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
loop-plannerEvaluate-Loop Step 1: PLAN. An agent skill from Ibrahim-3d/orchestrator-supaconductor.
Loop Planner is an agent skill from Ibrahim-3d/orchestrator-supaconductor. Evaluate-Loop Step 1: PLAN. Use this agent when starting a new track or feature to create a detailed execution plan. Reads spec.md, loads project context, and produces a phased plan.md with specific tasks, acceptance criteria, and dependencies. Triggered by: 'plan feature', 'create plan', 'start track', '/conductor implement' (planning phase).
Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Product & Project Management, covering User stories. The repository describes itself as: Multi-agent orchestration system for Claude Code with parallel execution, automated quality gates, Board of Directors, and bundled Superpowers skills. The licence is AGPL-3.0.
4 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 76c9b10. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown and json).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Loop Planner loads about 2.3k tokens when it runs. Until then it costs about 90 tokens; SKILL.md has 474 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check noted patterns worth knowing about, such as sudo or a known installer.
| `config`, `.json`, `.env` | `config` |Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from Ibrahim-3d/orchestrator-supaconductor at commit 76c9b10, republished under its AGPL-3.0 licence (© Ibrahim-3d). 474 words, ~2,347 tokens.
.claude/skills/loop-planner/SKILL.md (or your agent's skills folder).Creates detailed, scoped execution plans for tracks. This is Step 1 of the Evaluate-Loop.
spec.md — what needs to be builtconductor/tracks.md — what's already been done (to avoid overlap)plan.md (if exists) — check for prior progressread_file in order:
conductor/tracks.md — completed tracks and their deliverablesspec.md — requirements for this trackplan.md (if exists) — check what's already [x] doneconductor/product.md — product scope referenceconductor/tech-stack.md — technical constraintsBefore writing any plan:
spec.md asks for (deliverables)tracks.md)write_file plan.md with this structure (now includes dependency DAG for parallel execution):
# [Track Name] — Execution Plan
## Context
- **Track**: [ID]
- **Spec**: [one-line summary]
- **Dependencies**: [list prerequisite tracks]
- **Overlap Check**: [tracks checked, conflicts found/none]
- **Execution Mode**: PARALLEL | SEQUENTIAL
## Dependency Graph
<!-- YAML DAG for parallel execution -->
```yaml
dag:
nodes:
- id: "1.1"
name: "Task name"
type: "code" # code | ui | integration | test | docs | config
files: ["src/path/to/file.ts"]
depends_on: []
estimated_duration: "30m"
phase: 1
- id: "1.2"
name: "Another task"
type: "code"
files: ["src/another/file.ts"]
depends_on: []
phase: 1
- id: "1.3"
name: "Depends on 1.1 and 1.2"
type: "code"
files: ["src/path/to/file.ts"]
depends_on: ["1.1", "1.2"]
phase: 1
parallel_groups:
- id: "pg-1"
tasks: ["1.1", "1.2"]
conflict_free: true
- id: "pg-2"
tasks: ["1.3", "1.4"]
conflict_free: false
shared_resources: ["src/path/to/file.ts"]
coordination_strategy: "file_lock"<!-- deps: none, parallel: pg-1 --><!-- deps: none, parallel: pg-1 --><!-- deps: 1.1, 1.2 -->...
<!-- Add items here during execution if scope expansion is needed -->
### 3.1 DAG Generation Algorithm
When creating the plan, build the dependency graph:
```python
def generate_dag(tasks: list) -> dict:
"""
Generate DAG from task list.
1. Create nodes for each task
2. Analyze dependencies (explicit + file-based)
3. Identify parallel groups (tasks at same level with no conflicts)
4. Detect shared resources
"""
nodes = []
for task in tasks:
nodes.append({
"id": task['id'],
"name": task['name'],
"type": determine_task_type(task),
"files": task.get('files', []),
"depends_on": task.get('depends_on', []),
"estimated_duration": estimate_duration(task),
"phase": task['phase']
})
# Build adjacency list
dependents = defaultdict(list)
for node in nodes:
for dep in node['depends_on']:
dependents[dep].append(node['id'])
# Compute topological levels
levels = compute_topological_levels(nodes)
# Group tasks by level for parallel execution
parallel_groups = []
for level_num, level_tasks in enumerate(levels):
if len(level_tasks) >= 2:
# Analyze file conflicts
file_usage = defaultdict(list)
for task_id in level_tasks:
task = next(n for n in nodes if n['id'] == task_id)
for f in task.get('files', []):
file_usage[f].append(task_id)
# Find conflict-free groups
shared_files = {f: tasks for f, tasks in file_usage.items() if len(tasks) > 1}
if not shared_files:
parallel_groups.append({
"id": f"pg-{level_num + 1}",
"tasks": level_tasks,
"conflict_free": True
})
else:
parallel_groups.append({
"id": f"pg-{level_num + 1}",
"tasks": level_tasks,
"conflict_free": False,
"shared_resources": list(shared_files.keys()),
"coordination_strategy": "file_lock"
})
return {
"nodes": nodes,
"parallel_groups": parallel_groups
}Each task MUST follow the TDD bite-sized format. Every task is one focused action (2-5 minutes) with exact file paths and complete code:
### Task 1.1: [Component Name]
**Files:**
- Create: `exact/path/to/file.ts`
- Modify: `exact/path/to/existing.ts:123-145`
- Test: `tests/exact/path/to/test.ts`
**Step 1: Write the failing test**
```typescript
test('specific behavior', () => {
const result = function(input);
expect(result).toBe(expected);
});
```
**Step 2: Run test to verify it fails**
Run: `npm test -- --grep "specific behavior"`
Expected: FAIL with "function not defined"
**Step 3: Write minimal implementation**
```typescript
export function specificFunction(input: string): string {
return expected;
}
```
**Step 4: Run test to verify it passes**
Run: `npm test -- --grep "specific behavior"`
Expected: PASS
**Step 5: Commit**
```bash
git add tests/path/test.ts src/path/file.ts
git commit -m "feat: add specific feature"
```Key rules:
Automatically detect task type from description and files:
| Indicators | Type |
|---|---|
src/components/, .tsx, ui, component | ui |
api/, integration, supabase, stripe | integration |
.test.ts, test, coverage | test |
.md, docs, documentation | docs |
config, .json, .env | config |
| Default | code |
Tasks can run in parallel if:
Before finalizing, verify:
| Check | Question |
|---|---|
| Scoped | Does every task trace back to a spec.md requirement? |
| No Overlap | Does any task duplicate work from completed tracks? |
| Testable | Does every task have clear acceptance criteria? |
| Ordered | Are tasks sequenced by dependency? |
| Sized | Can each task be completed in a single session? |
Save the plan to the track's plan.md and report:
## Plan Created
**Track**: [track-id]
**Phases**: [count]
**Tasks**: [total count]
**Dependencies**: [list]
**Ready for**: Step 2 (Evaluate Plan) → hand off to loop-plan-evaluatorThe planner MUST update the track's metadata.json at key points:
{
"loop_state": {
"current_step": "PLAN",
"step_status": "IN_PROGRESS",
"step_started_at": "[ISO timestamp]",
"checkpoints": {
"PLAN": {
"status": "IN_PROGRESS",
"started_at": "[ISO timestamp]",
"agent": "loop-planner"
}
}
}
}{
"loop_state": {
"current_step": "EVALUATE_PLAN",
"step_status": "NOT_STARTED",
"checkpoints": {
"PLAN": {
"status": "PASSED",
"started_at": "[start timestamp]",
"completed_at": "[ISO timestamp]",
"agent": "loop-planner",
"commit_sha": "[if plan was committed]",
"plan_version": 1
},
"EVALUATE_PLAN": {
"status": "NOT_STARTED"
}
}
}
}metadata.jsonloop_state.checkpoints.PLAN fieldscurrent_step to EVALUATE_PLANmetadata.jsonIf metadata.json doesn't exist or is v1 format, create v2 structure with default values.
After creating the plan, the Conductor should dispatch the loop-plan-evaluator agent to verify the plan before execution begins.
© Ibrahim-3d, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in skills/loop-planner of Ibrahim-3d/orchestrator-supaconductor.
Open the folder on GitHubat commit 76c9b10
Loop Planner next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Loop Planner this skillIbrahim-3d/orchestrator-supaconductor | 380 | — | ~2.3k | Automated safety check: Notes | AGPL-3.0 | |
| Project Planneradrianpuiu/claude-skills-marketplace | 100 | 1 repos | ~6k | Automated safety check: Pass | None | |
| Sdd Work Decompositionmagnus919/hermes-profiles | 278 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Feature ForgeJeffallan/claude-skills | 12k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Refactor Design Reportpenwyp/ClaudePreference | 136 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Spec WorkflowTencentCloudBase/CloudBase-AI-Toolkit | 1.1k | 2 repos | ~1.3k | Automated safety check: Pass | MIT |
adrianpuiu/claude-skills-marketplace
Comprehensive project planning and documentation generator for software projects.
magnus919/hermes-profiles
SDD work decomposition — translates formal specifications into dependency-aware task plans with per-task acceptance criteria.
Jeffallan/claude-skills
Runs a structured requirements interview to produce a feature specification with EARS requirements, acceptance criteria and an implementation checklist.
penwyp/ClaudePreference
Produce a professional, code-grounded refactor or implementation design report from identified technical problems, product gaps, review findings, architecture concerns, or frontend-backend contract…
TencentCloudBase/CloudBase-AI-Toolkit
A skill your agent uses when medium-to-large changes need explicit requirements, technical design, and task planning before implementation, especially for multi-module work, unclear acceptance…
codingagentsystem/cas
Quick startup checklist for factory supervisors. An agent skill from codingagentsystem/cas.
Ibrahim-3d/orchestrator-supaconductor
Technical leadership guidance for engineering teams, architecture decisions, and technology strategy.
Ibrahim-3d/orchestrator-supaconductor
A skill your agent uses when working with Conductor's context-driven development methodology, managing project context artifacts, or understanding the relationship between product.md, tech-stack.md…
Ibrahim-3d/orchestrator-supaconductor
Creates specialized worker agents dynamically from templates.
Ibrahim-3d/orchestrator-supaconductor
Simulate a 5-member expert board deliberation for major decisions.
Ibrahim-3d/orchestrator-supaconductor
A skill your agent uses when completing a track that changes pricing, AI models, product features, or asset pipelines — syncs business context documents across all tiers.
Ibrahim-3d/orchestrator-supaconductor
Load project context efficiently for Conductor workflows. An agent skill from Ibrahim-3d/orchestrator-supaconductor.
Evaluate-Loop Step 1: PLAN. An agent skill from Ibrahim-3d/orchestrator-supaconductor. Loop Planner is an agent skill from Ibrahim-3d/orchestrator-supaconductor. Evaluate-Loop Step 1: PLAN.
Loop Planner fits situations like: tasks that involve User stories.
Run `npx skills add Ibrahim-3d/orchestrator-supaconductor --skill loop-planner -a claude-code`. Or copy the skill folder (skills/loop-planner in Ibrahim-3d/orchestrator-supaconductor) into .claude/skills/loop-planner in your project. Claude Code loads it when a task matches its description.
Run `npx skills add Ibrahim-3d/orchestrator-supaconductor --skill loop-planner -a codex`. Or copy the skill folder (skills/loop-planner in Ibrahim-3d/orchestrator-supaconductor) into .agents/skills/loop-planner in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Ibrahim-3d/orchestrator-supaconductor --skill loop-planner -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/loop-planner, .gemini/skills/loop-planner, .github/skills/loop-planner and .opencode/skills/loop-planner in your project.
SKILL.md names no scripts, command-line tools or credentials: Loop Planner is instructions for the agent only. Our summary lists: Python 3.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
Loop Planner is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.3k tokens (SKILL.md is roughly 9.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Loop Planner: Project Planner (adrianpuiu/claude-skills-marketplace, 100 stars), Sdd Work Decomposition (magnus919/hermes-profiles, 278 stars), Feature Forge (Jeffallan/claude-skills, 12k stars) and Refactor Design Report (penwyp/ClaudePreference, 136 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Ibrahim-3d (a GitHub user) maintains it in Ibrahim-3d/orchestrator-supaconductor, which has 380 GitHub stars. The repository holds 27 skills in this directory. The repository was last updated on September 27, 2026.
Source: Ibrahim-3d/orchestrator-supaconductor on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.