customise-workflow
Customise the prd-taskmaster plugin workflow via curated brainstorm questions. The AI asks, the user answers in plain English, and the skill writes their preferences to .atlas-ai/config/atlas.json. Future runs of prd-taskmaster read that file and apply user preferences to phase gates, validation strictness, default provider, preferred execution mode, and template choice. For deeper tweaks beyond the curated questions, users can hand-edit files in .atlas-ai/customizations/. Use when the user says "customise workflow", "customize workflow", "adjust my PRD settings", "tune the skill", or wants to
npx skills add anombyte93/prd-taskmaster --skill customise-workflow --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.
# customise-workflow AI-driven workflow customisation for the `prd-taskmaster` plugin. Replaces manual JSON editing. Part of the plugin's companion-skills family. **Script**: `skills/customise-workflow/script.py` (all commands output JSON) **Plugin config root**: `.atlas-ai/` (per-project, lives alongside TaskMaster's `.taskmaster/`) ## When to Use Activate when the user says: "customise workflow", "customize workflow", "adjust PRD settings", "tune the skill", "change my defaults", or "personalise prd-taskmaster". Skip: generating a new PRD (use `/prd:go`), executing tasks (use HANDOFF modes), or running research expansion (use `/expand-tasks`). ## The One Rule **The AI asks the questions and writes the config. The user never manually edits JSON. The config file is the output, not the input.** If the user wants tweaks beyond the curated questions, point them at `.atlas-ai/customizations/` (see "Customizations directory" below) — do not hand them raw JSON. ## Flow ``` LOAD → ASK → VALIDATE → WRITE → VERIFY ``` ### Phase 1: LOAD current config Run the script to load existing preferences (or defaults if first run): ```bash python3 skills/customise-workflow/script.py load-config ``` Re
- When to Use
- The One Rule
- Flow
- Phase 1: LOAD current config
- Phase 2: ASK curated questions
- Phase 3: VALIDATE answers
- Phase 4: WRITE config
- Phase 5: VERIFY
- Script Commands Reference
- Config Schema
- Customizations directory
- Critical Rules
python3 skills/customise-workflow/script.py load-config python3 skills/customise-workflow/script.py validate-answer \ python3 skills/customise-workflow/script.py write-config --input /tmp/answers.json python3 skills/customise-workflow/script.py show-config
What does the customise-workflow skill do?
Customise the prd-taskmaster plugin workflow via curated brainstorm questions. The AI asks, the user answers in plain English, and the skill writes their preferences to .atlas-ai/config/atlas.json. Future runs of prd-taskmaster read that file and apply user preferences to phase gates, validation strictness, default provider, preferred execution mode, and template choice. For deeper tweaks beyond the curated questions, users can hand-edit files in .atlas-ai/customizations/. Use when the user says "customise workflow", "customize workflow", "adjust my PRD settings", "tune the skill", or wants to
How do I install it?
Run `npx skills add anombyte93/prd-taskmaster --skill customise-workflow --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.