Generate structured Markdown PRDs for ML and MLOps initiatives.
npx skills add https://github.com/dobraga/dotfiles --skill prd-ml
Please help me install this Agent Skill. Skill: prd-ml Source: https://github.com/dobraga/dotfiles/tree/main/.claude/skills/prd-ml Command: npx skills add https://github.com/dobraga/dotfiles --skill prd-ml
Generate comprehensive Product Requirements Documents for data science, machine learning, and MLOps initiatives to align teams and formalize project scope.
Provide a feature description and I will generate a complete PRD draft saved under docs/tasks/prd-[feature-name].md.
High-intent search queries and answers about installing and using this skill.
Generate a machine learning PRD by providing a feature description to produce a structured Markdown document covering data requirements, model specifications, evaluation metrics, and MLOps deployment considerations.
A data science product requirements document should include sections for goals, background, data requirements, model and algorithm specifications, evaluation criteria, user stories, risks, non-goals, success metrics, and open questions.
Yes, you can plan data pipelines and ML deployment infrastructure by drafting PRDs that cover end-to-end lifecycle planning from data acquisition to deployment considerations for data science and MLOps initiatives.
The best way to structure an MLOps initiative document is to use a standardized PRD template with dedicated sections for data requirements, model algorithms, evaluation, and risks, outputting a ready-to-use Markdown file.
You save a drafted PRD for a data science project by outputting the final structured Markdown document to the file path docs/tasks/prd-[feature-name].md for version control and team access.
thepriceisrightGenerate a structured PRD from a feature brief and save it to tasks/prd-[feature-name].md.
Davie521Synthesize a structured PRD from conversation context and project files.
IvanWeissVanDerPolAutomate end-to-end ML pipeline construction and evaluation.
dralgorhythmGenerate Product Requirements Documents with user stories and Given/When/Then acceptance criteria.
