setup
Phase 0 of the prd-taskmaster pipeline. Resolves the active backend, initializes the project, configures the provider stack when the TaskMaster backend is active (DETECT-FIRST — never overwrite a working user config), and verifies the AI pipeline. Autonomous: zero user questions unless a hard block is hit. Declares the Setup phase complete so DISCOVER can follow.
npx skills add anombyte93/prd-taskmaster --skill setup --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Phase 0: Setup Declarative phase skill. Invoked by the prd-taskmaster orchestrator when `current_phase` is null or `SETUP`. Never called directly by a user. ## Entry gate 1. Call `mcp__plugin_prd_go__check_gate(phase="SETUP", evidence={})` for diagnostics. `check_gate` is an EXIT gate: it verifies you have the evidence to *advance*, not to *enter*. On first entry you have no evidence yet (Step 4 below produces `validate_setup.ready=true`), so a `gate_passed: false` result here is EXPECTED — the state machine's legal transitions (`None → SETUP`) already guarantee only legal entry. - **First entry** (no evidence yet): note the result and continue with the Procedure. - **Re-entry**: if the gate reports violations, report them and stop — it protects against re-running a completed phase or skipping ahead. Enforce the gate when you ADVANCE (after the procedure), not on entry. ## Procedure (5 steps, abort on hard failure) ### Step 1: Backend detection Run backend detection: ```bash python3 script.py backend-detect ``` The native engine is the sole generator and needs no external binary — a keyless host CLI (`claude` / `codex` / `gemini`) on PATH, or a provider API key, is sufficient (se
- Entry gate
- Procedure (5 steps, abort on hard failure)
- Step 1: Backend detection
- Step 2: Project init
- Step 2.5: Customisation bootstrap (REQUIRED — closes execute-task deadlock)
- Step 3: Provider configuration — DETECT-FIRST
- Step 4: Probe test
- Step 5: Status line
- Exit gate
- Red flags (stop and report, do not paper over)
- Non-exits
python3 script.py backend-detect
python3 script.py init-project
mkdir -p .atlas-ai/customizations
if [ ! -f .atlas-ai/customizations/system-prompt-template.md ]; then
if [ -d "$PLUGIN_SKEL" ]; then
cp -n "$PLUGIN_SKEL"/*.md .atlas-ai/customizations/ # -n: no-clobber, copy starter pack
else
fi
if [ ! -f .atlas-ai/ship-check.py ] && [ -f "${CLAUDE_PLUGIN_ROOT}/skel/ship-check.py" ]; then
cp "${CLAUDE_PLUGIN_ROOT}/skel/ship-check.py" .atlas-ai/ship-check.pyWhat does the setup skill do?
Phase 0 of the prd-taskmaster pipeline. Resolves the active backend, initializes the project, configures the provider stack when the TaskMaster backend is active (DETECT-FIRST — never overwrite a working user config), and verifies the AI pipeline. Autonomous: zero user questions unless a hard block is hit. Declares the Setup phase complete so DISCOVER can follow.
How do I install it?
Run `npx skills add anombyte93/prd-taskmaster --skill setup --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From anombyte93/prd-taskmaster, a repository with 586 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.