003-skills/.claude/skills/nixtla-prd-to-code/SKILL.md
Transform PRD documents into actionable implementation tasks with TodoWrite integration. Use when planning development work, converting requirements to tasks, or creating implementation roadmaps. Trigger with 'PRD to tasks', 'plan implementation from PRD', or 'create task list'.
npx skillsauth add intent-solutions-io/plugins-nixtla nixtla-prd-to-codeInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Transform Product Requirements Documents into comprehensive implementation task lists with automatic TodoWrite integration for seamless development planning.
This skill bridges the gap between requirements and code:
Required:
Optional:
pyyaml: For YAML task list export (install via pip install pyyaml)Locate the PRD file to transform:
ls 000-docs/000a-planned-plugins/*/02-PRD.md
Execute the PRD parser to extract requirements:
python {baseDir}/scripts/parse_prd.py \
--prd 000-docs/000a-planned-plugins/implemented/nixtla-roi-calculator/02-PRD.md \
--output tasks.json
The script generates a structured task list with:
Automatically populate Claude's todo list:
python {baseDir}/scripts/parse_prd.py \
--prd 000-docs/000a-planned-plugins/implemented/nixtla-roi-calculator/02-PRD.md \
--populate-todo
Follow the generated task list, marking items complete as work progresses.
Error: PRD file not found
Solution: Verify PRD path, check 000-docs/000a-planned-plugins/ directory
Error: Missing Functional Requirements section
Solution: Ensure PRD has ## Functional Requirements heading with FR-X items
Error: TodoWrite tool not available
Solution: Skill can only populate todos in conversation context, not standalone script execution
Error: Invalid PRD format
Solution: PRD must have standard sections: Overview, Goals, Functional Requirements, Technical Spec
Error: Circular dependency detected
Solution: Review task dependencies, ensure no circular references (Task A → Task B → Task A)
python {baseDir}/scripts/parse_prd.py \
--prd 000-docs/000a-planned-plugins/implemented/nixtla-roi-calculator/02-PRD.md \
--output roi_tasks.json \
--verbose
Generated tasks.json:
{
"tasks": [
{
"id": "roi-001",
"title": "Implement cost input collection",
"description": "Build input form for infrastructure costs, forecasting volume, team composition",
"priority": "P0",
"dependencies": [],
"complexity": "medium",
"functional_requirement": "FR-1"
},
{
"id": "roi-002",
"title": "Build ROI calculation engine",
"description": "5-year TCO calculation for build vs. buy scenarios",
"priority": "P0",
"dependencies": ["roi-001"],
"complexity": "high",
"functional_requirement": "FR-2"
}
]
}
When used in conversation context:
# In Claude Code conversation
from parse_prd import PRDParser
parser = PRDParser('000-docs/000a-planned-plugins/implemented/nixtla-roi-calculator/02-PRD.md')
tasks = parser.extract_tasks()
# Automatically populates TodoWrite
for task in tasks:
TodoWrite(content=task['title'], activeForm=f"Working on {task['title']}", status="pending")
python {baseDir}/scripts/parse_prd.py \
--prd 000-docs/000a-planned-plugins/implemented/nixtla-forecast-explainer/02-PRD.md \
--output-format markdown \
--output implementation_plan.md
Generated implementation_plan.md:
# Nixtla Forecast Explainer - Implementation Plan
## Phase 1: Core Infrastructure (P0)
- [ ] Set up project structure and dependencies
- [ ] Create MCP server scaffold
- [ ] Implement SHAP explainability integration
## Phase 2: Feature Development (P0)
- [ ] Build feature importance calculation
- [ ] Implement counterfactual analysis
- [ ] Add time-based contribution decomposition
## Phase 3: Visualization (P1)
- [ ] Generate waterfall charts
- [ ] Create interactive dashboards
- [ ] Export to PDF reports
for prd in 000-docs/000a-planned-plugins/*/02-PRD.md; do
plugin_name=$(basename $(dirname "$prd"))
python {baseDir}/scripts/parse_prd.py \
--prd "$prd" \
--output "009-temp-data/task-plans/${plugin_name}_tasks.json"
done
000-docs/000a-planned-plugins/README.md (PRD structure specification)AskUserQuestion to learn about TodoWrite tool capabilitiesbd CLI) for advanced task trackingRelated Skills:
nixtla-plugin-scaffolder: Generate plugin structure from PRDnixtla-demo-generator: Create Jupyter demos for implementationnixtla-test-generator: Build test suites from PRD requirementsScripts:
{baseDir}/scripts/parse_prd.py: Main PRD parsing and task generation script{baseDir}/assets/templates/task_template.json: Task structure templatetesting
This skill enables Claude to manage isolated test environments using Docker Compose, Testcontainers, and environment variables. It is used to create consistent, reproducible testing environments for software projects. Claude should use this skill when the user needs to set up a test environment with specific configurations, manage Docker Compose files for test infrastructure, set up programmatic container management with Testcontainers, manage environment variables for tests, or ensure cleanup after tests. Trigger terms include "test environment", "docker compose", "testcontainers", "environment variables", "isolated environment", "env-setup", and "test setup".
tools
This skill uses the test-doubles-generator plugin to automatically create mocks, stubs, spies, and fakes for unit testing. It analyzes dependencies in the code and generates appropriate test doubles based on the chosen testing framework, such as Jest, Sinon, or others. Use this skill when you need to generate test doubles, mocks, stubs, spies, or fakes to isolate units of code during testing. Trigger this skill by requesting test double generation or using the `/gen-doubles` or `/gd` command.
tools
This skill enables Claude to generate realistic test data for software development. It uses the test-data-generator plugin to create users, products, orders, and custom schemas for comprehensive testing. Use this skill when you need to populate databases, simulate user behavior, or create fixtures for automated tests. Trigger phrases include "generate test data", "create fake users", "populate database", "generate product data", "create test orders", or "generate data based on schema". This skill is especially useful for populating testing environments or creating sample data for demonstrations.
development
This skill analyzes code coverage metrics to identify untested code and generate comprehensive coverage reports. It is triggered when the user requests analysis of code coverage, identification of coverage gaps, or generation of coverage reports. The skill is best used to improve code quality by ensuring adequate test coverage and identifying areas for improvement. Use trigger terms like "analyze coverage", "code coverage report", "untested code", or the shortcut "cov".