
Council
- 1 installs
- Updated August 5, 2026
- cristian-pisco/jelou-spec-plugin
Run spec-driven development workflows with multi-service coordination and agent specialization.
About
Jelou Spec Plugin provides TDD-driven spec orchestration across Claude Code, OpenCode, and Codex. Coordinates multi-service tasks with dependency-driven execution.
- Spec-driven workflow orchestration
- Multi-service task coordination
Council by the numbers
- 1 all-time installs (skills.sh)
- Ranked #2,479 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/cristian-pisco/jelou-spec-plugin --skill councilAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1 |
|---|---|
| Last updated | August 5, 2026 |
| Repository | cristian-pisco/jelou-spec-plugin ↗ |
What it does
Run spec-driven development workflows with multi-service coordination and agent specialization.
Files
You are the orchestrator for the /jlu-council command.
Phase 1 — Bootstrap
Resolve plugin root. Try in order: 1. Go up 2 levels from this skill's directory (plugin install at <plugin-root>/skills/council/SKILL.md). 2. ~/.claude/jelou/ (manual installation).
If neither resolves, stop with: "Plugin root not found. Ensure jelou-spec-plugin is installed."
Runtime contract (Claude Code). The workflow file uses OpenCode names:
- Workflow says
question→ invokeAskUserQuestion(deferred — preload below). - Workflow §4.3 says "research each uncertainty with your runtime's web research tool" →
use the Perplexity MCP tool if connected (mcp__perplexity__*), otherwise WebSearch (preload below). The judges never search — only you, the arbiter, do. Never assume a fact you cannot verify.
- Workflow §6 says "invoke
/jlu-new-task" → invoke thenew-taskskill via theSkill
tool, passing the seed text as its argument. This is the council's ONLY onward routing — never suggest or invoke superpowers, GSD, gstack, or any other plugin's planning/spec workflow. Prefer the fresh-session handoff in §6 when the deliberation grew long.
- Never narrate questions as plain text. Never skip a prescribed question.
Run these in parallel (single tool-call message — do NOT serialize): 1. Bash: <plugin-root>/bin/check-update.sh 2>/dev/null || echo SKIPPED 2. Read: <plugin-root>/jelou/workflows/council.md 3. ToolSearch: select:AskUserQuestion,WebSearch (max_results: 2) — AskUserQuestion is mandatory before any question; WebSearch is the arbiter's fallback research tool. 4. ToolSearch: perplexity search (max_results: 3) — best-effort probe for the Perplexity MCP tool; if it returns matches, prefer it over WebSearch for §4.3 research.
Update banner. If the bash output starts with UPDATE_AVAILABLE <local> <remote>, print one line and continue:
[jlu] v<remote> available (you have v<local>). Run: /plugin update jlu@jelou-spec-pluginIf the output is UP_TO_DATE or SKIPPED, continue silently. Update-check failures must never block the workflow.
ToolSearch fallback. If ToolSearch returns zero matches for AskUserQuestion, fall back to printing each question as plain text and warn the user that the skill cannot run correctly without AskUserQuestion in this Claude Code version. If neither Perplexity nor WebSearch is available, the arbiter must declare each judge uncertainty as unresolved rather than assuming it away (per the workflow's §4.3).
Phase 2 — Execute Workflow
Follow the workflow file you just read. Do NOT spawn a sub-agent — execute the workflow yourself in this session (you are the arbiter; the design forbids delegating the synthesis). The deliberation runs over several rounds until the user and the jury reach consensus; you stay in this session for the whole loop, the inter-round research, and the final /jlu-new-task handoff.
The argument is {argument}. The plugin root is the path resolved above. The current working directory is {cwd}.