From orchestrator-supaconductor
Generates TDD implementation plans with bite-sized tasks, exact file paths, tests, code, commands, and commits for multi-step features from specs. Integrates with conductor tracks.
npx claudepluginhub ibrahim-3d/orchestrator-supaconductor --plugin orchestrator-supaconductorThis skill uses the workspace's default tool permissions.
Write comprehensive implementation plans assuming the engineer has zero context for our codebase and questionable taste. Document everything they need to know: which files to touch for each task, code, testing, docs they might need to check, how to test it. Give them the whole plan as bite-sized tasks. DRY. YAGNI. TDD. Frequent commits.
Generates detailed TDD implementation plans for multi-step tasks from specs, breaking into 2-5 minute steps with exact file paths, code snippets, tests, commands, and git commits. Use before coding.
Creates TDD implementation plans for multi-step features from specs, with granular tasks, exact file paths, code/tests/commands, and git commits. Use before coding.
Generates detailed implementation plans from specs for multi-step tasks before coding, with TDD bite-sized steps, file structure mapping, and task decomposition.
Share bugs, ideas, or general feedback.
Write comprehensive implementation plans assuming the engineer has zero context for our codebase and questionable taste. Document everything they need to know: which files to touch for each task, code, testing, docs they might need to check, how to test it. Give them the whole plan as bite-sized tasks. DRY. YAGNI. TDD. Frequent commits.
Assume they are a skilled developer, but know almost nothing about our toolset or problem domain. Assume they don't know good test design very well.
Announce at start: "I'm using the writing-plans skill to create the implementation plan."
Save plans to: The active conductor track directory: conductor/tracks/{track_id}/plan.md
If no conductor track exists, create one first using the /orchestrator-supaconductor:new-track flow.
Each step is one action (2-5 minutes):
Every plan MUST start with this header:
# [Feature Name] Implementation Plan
> **For Claude:** REQUIRED SUB-SKILL: Use orchestrator-supaconductor:executing-plans to implement this plan task-by-task.
**Goal:** [One sentence describing what this builds]
**Architecture:** [2-3 sentences about approach]
**Tech Stack:** [Key technologies/libraries]
---
### Task N: [Component Name]
**Files:**
- Create: `exact/path/to/file.py`
- Modify: `exact/path/to/existing.py:123-145`
- Test: `tests/exact/path/to/test.py`
**Step 1: Write the failing test**
```python
def test_specific_behavior():
result = function(input)
assert result == expected
```
**Step 2: Run test to verify it fails**
Run: `pytest tests/path/test.py::test_name -v`
Expected: FAIL with "function not defined"
**Step 3: Write minimal implementation**
```python
def function(input):
return expected
```
**Step 4: Run test to verify it passes**
Run: `pytest tests/path/test.py::test_name -v`
Expected: PASS
**Step 5: Commit**
```bash
git add tests/path/test.py src/path/file.py
git commit -m "feat: add specific feature"
```
This skill is part of the Conductor workflow. All plans are saved to the active track directory.
When invoked by the Conductor orchestrator (with --track-dir and --spec parameters):
--spec pathconductor/product.md, conductor/tech-stack.md{--track-dir}/plan.mdmetadata.json checkpoint to PLAN: PASSEDWhen invoked standalone (no parameters):
conductor/tracks.mdspec.md for requirementsconductor/tracks/{track_id}/plan.mdmetadata.json checkpoint to PLAN: PASSED/orchestrator-supaconductor:implement or /orchestrator-supaconductor:go to execute