About

Imported from akillness/jeo-skills (.agent-skills/to-prd/SKILL.md). Install upstream with npx skills add akillness/jeo-skills --skill to-prd. Copyright stays with the author.

To PRD

Name: to-prd
Author: akillness

Convert current conversation context into a structured PRD for publication to the project issue tracker.

When to use this skill

Documenting requirements from existing discussion
Creating a formal spec before breaking work into issues
Recording architectural decisions alongside user stories

When not to use this skill

Breaking work into tickets → use to-issues
Writing technical internal docs → use technical-writing
Quick task notes → use task-planning

Process

1. Explore and understand

Review the codebase using the project's domain vocabulary (CONTEXT.md) and relevant ADRs. Do not interview the user — synthesize from existing context.

2. Design modules

Identify the major components to build or modify. Emphasize deep modules: simple, testable interfaces with stable contracts. Validate assumptions with the user and confirm which modules need test coverage.

3. Document and publish

Complete the PRD template and submit to the issue tracker with the needs-triage label.

PRD template

# [Feature/Change Name]

## Problem Statement

[User-facing description of the issue or opportunity. What pain does this solve?]

## Solution

[User-facing description of the resolution approach.]

## User Stories

1. As a [actor], I want [feature], so that [benefit].
2. As a [actor], I want [feature], so that [benefit].
[... comprehensive list covering all use cases]

## Implementation Decisions

### Modules

[Major components to build/modify with interface descriptions]

### Technical Choices

[Architecture decisions, schema design, API contracts — avoid file paths and code snippets]

### ADR References

[Links to relevant Architecture Decision Records]

## Testing Decisions

[Testing philosophy for this feature, which modules need coverage, relevant test precedents]

## Out of Scope

- [Explicitly excluded item]
- [Explicitly excluded item]

## Further Notes

[Additional context, open questions, or dependencies]

Quality checklist

Problem statement is user-facing (not technical)
User stories cover all actors and use cases
Implementation decisions reference existing domain vocabulary
Out of scope section prevents scope creep
No file paths or code in the PRD (these belong in issues)

Instructions

Identify the task trigger and expected output.
Follow the workflow steps in this skill from top to bottom.
Validate outputs before moving to the next step.
Capture blockers and fallback path if any step fails.

Examples

Example: Apply this skill to a small scope first, then scale to full scope after validation passes.

Best practices

Keep outputs deterministic and auditable.
Prefer small reversible changes over broad risky edits.
Record assumptions explicitly.

References

Project standards: .agent-skills/skill-standardization/SKILL.md
Validator script: .agent-skills/skill-standardization/scripts/validate_skill.sh

Use it

Copy one of these into your project. Installing also returns the manifest and these snippets.

yaml

targets:
  - https://api.opensmartroute.ai/api/v1/registry/akillness-jeo-skills-to-prd/manifest   # or paste the manifest below

Manifest

An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.

akillness-jeo-skills-to-prd.ocm.jsonjson

{
  "ocm": "1",
  "id": "akillness-jeo-skills-to-prd",
  "kind": "skill",
  "name": "to-prd",
  "description": "Generate structured PRD from conversation context without interviewing the user",
  "publisher": "akillness",
  "version": "1.0.0",
  "capabilities": {
    "domains": [
      "general"
    ],
    "tags": [
      "skill-md",
      "prd",
      "requirements",
      "product",
      "documentation",
      "planning",
      "user-stories",
      "skills-sh"
    ],
    "languages": [
      "en"
    ]
  },
  "quality_prior": 0.6,
  "examples": [
    "Generate structured PRD from conversation context without interviewing the user"
  ],
  "primary": false,
  "metadata": {
    "source": {
      "provider": "skills.sh",
      "repository": "https://github.com/akillness/jeo-skills",
      "path": ".agent-skills/to-prd/SKILL.md",
      "ref": "HEAD",
      "url": "https://github.com/akillness/jeo-skills/blob/HEAD/.agent-skills/to-prd/SKILL.md",
      "key": "akillness/jeo-skills/.agent-skills/to-prd/SKILL.md"
    },
    "compatibility": "Works with any issue tracker. Run setup-matt-pocock-skills first to configure tracker location and triage label vocabulary. Pairs with to-issues for decomposition and triage for state management.\n",
    "allowed_tools": [
      "Read",
      "Grep",
      "Glob",
      "Bash",
      "Write",
      "Edit"
    ]
  },
  "instructions": "# To PRD\n\nConvert current conversation context into a structured PRD for publication to the project issue tracker.\n\n## When to use this skill\n\n- Documenting requirements from existing discussion\n- Creating a formal spec before breaking work into issues\n- Recording architectural decisions alongside user stories\n\n## When not to use this skill\n\n- Breaking work into tickets → use `to-issues`\n- Writing technical internal docs → use `technical-writing`\n- Quick task notes → use `task-planning`\n\n## Process\n\n### 1. Explore and understand\n\nReview the codebase using the project's domain vocabulary (CONTE",
  "cost": {
    "context_tokens": 746
  }
}

Fetch it by URL: GET /api/v1/registry/akillness-jeo-skills-to-prd/manifest?version=1.0.0

Reviews

Star ratings from people who tried it. One review per account; edit yours any time.

No reviews yet. Install it, try it, and be the first to rate it.