Convert rough requirements or Jira tickets into a draft PRD with frontmatter.
npx skills add https://github.com/lekman/cdn --skill refine-lekman
Please help me install this Agent Skill. Skill: refine Source: https://github.com/lekman/cdn/tree/main/.claude/skills/refine Command: npx skills add https://github.com/lekman/cdn --skill refine-lekman
Refine helps convert rough requirements, Jira tickets, or text descriptions into a structured PRD that can be handed to the planner skill, reducing ambiguity and ensuring a single, independently deployable scope per PRD.
Provide a Jira ticket reference or paste your requirements, and I will generate a draft PRD.
High-intent search queries and answers about installing and using this skill.
To convert a rough Jira ticket into a structured PRD, provide the ticket reference to gather context and draft a scoped document with acceptance criteria and frontmatter. It anchors the requirements and outputs a planner-compatible draft.
To identify missing requirements before drafting a PRD, the tool analyzes the text description to find gaps and generates targeted clarifying questions. This resolves uncertainties to ensure a single, independently deployable scope per document.
The best way to scope a PRD for a single deployable feature is to refine rough requirements into a planner-compatible template. This reduces ambiguity by generating a structured document with clear acceptance criteria and frontmatter.
Yes, you can generate a planner-compatible PRD directly from a Jira ticket reference. The system gathers context from the ticket and related docs to anchor the draft, providing a seamless handoff path to the planner.
A key limitation is that the initial draft relies on the context available in the provided Jira ticket or text description. You must manually resolve the generated clarifying questions before handoff to ensure the PRD scope is fully validated.
kvnxiaoCreate per-ticket git worktrees and generate GitHub PRs for Linear tickets.
reggiechan74Validate execution plans for completeness, clarity, measurability, and acceptance criteria.
okwindsTransform a PRD into an implementation-ready engineering specification with architecture, data modeling, API design, security, deployment, and testing.
tobyileeGenerate structured PRDs with requirements, user stories, and acceptance criteria.
