Convert Product Requirement Documents into structured tasks.md implementation plans.
npx skills add https://github.com/mbed92/phd --skill clavix-plan-mbed92
Please help me install this Agent Skill. Skill: clavix-plan Source: https://github.com/mbed92/phd/tree/main/.skills/clavix-plan Command: npx skills add https://github.com/mbed92/phd --skill clavix-plan-mbed92
This Skill automates the process of breaking down Product Requirement Documents (PRDs) into detailed, actionable technical tasks, ensuring alignment with existing codebase architecture and conventions.
tasks.md file with specific file paths, implementation details, and task IDs, following best practices for granularity and sequencing.Use the clavix-plan skill to generate an implementation plan for the project based on the provided PRD.
High-intent search queries and answers about installing and using this skill.
To convert a PRD into actionable developer tasks, this Skill analyzes your existing codebase architecture, dependencies, and conventions to generate a structured tasks.md file with specific file paths, implementation notes, and task IDs.
Yes, you can generate a technical implementation plan that matches your project architecture. The Skill scans your project structure, dependencies, and coding patterns to ensure all generated tasks align with your specific tech stack and conventions.
The best way to break down product requirements into a task list with specific file paths is to ingest your PRD document and let the Skill automatically sequence tasks based on project standards, best practices for task granularity, and detected file structures.
PRD task generation works with frameworks like Next.js, Tailwind CSS, and Zustand. The Skill detects your specific tech stack during codebase analysis and tailors the generated implementation details to match your state management and styling patterns.
To create an implementation plan for a new user authentication feature from a PRD, provide the requirement document to the Skill. It will output a precise list of tasks including creating specific files for API endpoints, UI components, and validation schemas.
When generating technical documentation from a PRD, limitations include relying entirely on the accuracy of your provided requirement documents and the Skill's ability to detect existing codebase conventions, meaning unstructured or highly ambiguous PRDs may yield less precise task sequencing.
pretodevGenerate structured feature specification documents from feature definitions.
tacogipsConvert design documents into implementation plans with task breakdowns and progress tracking.
g5becksTransform PRD documents into dependency-aware technical task breakdowns with file paths.
michael-harrisOrchestrate project planning with requirements gathering, codebase research, and PRD generation.