clavix-plan

Transform PRD documents into dependency-aware technical task breakdowns with file paths.

Updated Feb 22, 2026
One-click install
npx skills add https://github.com/g5becks/oxlint-plugins --skill clavix-plan-g5becks
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: clavix-plan
Source: https://github.com/g5becks/oxlint-plugins/tree/main/.skills/clavix-plan
Command: npx skills add https://github.com/g5becks/oxlint-plugins --skill clavix-plan-g5becks

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of transforming high-level Product Requirement Documents (PRDs) into detailed, actionable technical tasks for software development, ensuring alignment with existing codebase architecture.

Core Features & Use Cases

  • Codebase Analysis: Scans project structure, dependencies, and coding patterns (state management, styling, API calls).
  • PRD Ingestion: Reads requirements from PRD documents.
  • Task Generation: Creates specific, file-path-oriented tasks with dependencies and estimates, adhering to project conventions.
  • Use Case: After writing a new feature's PRD, use this Skill to generate a precise list of files to create or modify, the exact code patterns to follow, and the order of operations for the development team.

Quick Start

Use the clavix-plan skill to analyze the current project and generate a technical plan for the new user authentication feature described in the PRD.

Frequently Asked Questions about clavix-plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn a PRD into actionable development tasks?▼

To turn a PRD into actionable development tasks, this Skill analyzes your existing codebase patterns and generates dependency-aware technical task breakdowns with specific file paths and implementation details.

What is codebase analysis for technical task generation?▼

Codebase analysis for technical task generation scans your project's directory structure, framework, styling, state management, and API conventions to ensure generated tasks adhere to your project's architecture.

How do I generate a development plan that follows my existing project conventions?▼

You can generate a development plan that follows existing conventions by ingesting your PRD alongside a codebase analysis, which produces specific implementation tasks matching your framework and API patterns.

Can I create file-path-oriented tasks from a product requirements document?▼

Yes, you can create file-path-oriented tasks from a product requirements document by processing the PRD to output a structured plan detailing exact files to create or modify and their execution order.

Does PRD task generation work without specifying dependencies?▼

PRD task generation works without external dependencies, but it requires an existing codebase to analyze directory structure and coding patterns to produce dependency-aware estimates and accurate technical tasks.

What are the limitations of automated technical task breakdown?▼

Automated technical task breakdown relies entirely on analyzing existing codebase patterns and PRD content, meaning it cannot generate accurate implementation tasks for empty projects or requirements lacking sufficient technical detail.