Prd Taskmaster
Zero-config goal-to-tasks engine (the Atlas engine).
Install
npx skills add anombyte93/prd-taskmaster --skill prd-taskmaster -g -a claude-code -y- Repository
- anombyte93/prd-taskmaster606
- Category
- Security
- Updated
- 3mo ago
- License
- MIT
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
Zero-config goal-to-tasks engine (the Atlas engine). Takes any goal (software, pentest, business, learning), runs adaptive discovery via brainstorming, generates a validated spec, parses into TaskMaster tasks, and hands off to execution. Use when user says "PRD", "product requirements", "I want to build", invokes /atlas, or wants task-driven development.
prd-taskmaster, the Atlas engine
Zero-config goal-to-tasks engine. AI handles discovery and content; the engine backend (MCP
server preferred, script.py fallback, see Phase 0) handles mechanics.
Command: /atlas is the canonical invocation (or /prd-taskmaster, or just say "I want to
build …"). The full plugin install also exposes phase skills; this standalone skill runs the whole
pipeline inline.
Script: ~/.claude/skills/prd-taskmaster/script.py (all commands output JSON). It is a thin
shim over the bundled prd_taskmaster/ package, the single source of truth shared with the plugin.
Manual flag: If the user says --manual, manual=true, or "do it manually", perform the
TaskMaster mechanics yourself: write .taskmaster/docs/prd.md, write .taskmaster/tasks/tasks.json
with tasks and subtasks, run validate-tasks, then run enrich-tasks. Do not block on TaskMaster
CLI/MCP parsing.
When to Use
Activate: PRD, product requirements, taskmaster, task-driven development, "I want to build X", any goal. Skip: API docs, test specs, project timelines, PDF creation.
Phase 0: Engine Backend Resolution (MANDATORY, before any other engine operation)
The engine has two interchangeable backends: the atlas-engine MCP server (preferred) and script.py (zero-dependency fallback). Resolve which one this session uses NOW. Do NOT silently default to script.py.
Claude Code note, deferred tools: MCP tools are often deferred: their names appear
in a system-reminder list but they are NOT callable until you load their schemas with the
ToolSearch tool. "I don't see a callable engine_preflight tool" does NOT mean the server
is absent, it almost always means you have not run ToolSearch yet.
Resolution procedure, in order:
