Run any Skill in Manus with one click

to-prd

Stars0

Forks0

UpdatedMay 15, 2026 at 18:02

Turn the current conversation context into a PRD and submit it as a GitHub issue. Use when user wants to create a PRD from the current context.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

vinayprograms

vinayprograms/agent-skills

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Project Management SpecialistsBusiness and Financial Operations Occupations·SOC 13-1082

File Explorer

2 files

SKILL.md

readonly

name	to-prd
description	Turn the current conversation context into a PRD and submit it as a GitHub issue. Use when user wants to create a PRD from the current context.

This skill takes the current conversation context and codebase understanding and produces a PRD. Do NOT interview the user — just synthesize what you already know.

Process

Explore the repo to understand the current state of the codebase, if you haven't already.
Sketch out the major modules you will need to build or modify to complete the implementation. Actively look for opportunities to extract deep modules that can be tested in isolation.

A deep module (as opposed to a shallow module) is one which encapsulates a lot of functionality in a simple, testable interface which rarely changes.

Check with the user that these modules match their expectations. Check with the user which modules they want tests written for.

Write the PRD using the template below and write it to docs/PRD.md.

## Problem Statement

The problem that the user is facing, from the user's perspective.

## Solution

The solution to the problem, from the user's perspective.

## User Stories

A LONG, numbered list of user stories. Each user story should be in the format of:

1. As an <actor>, I want a <feature>, so that <benefit>

<user-story-example>
1. As a mobile bank customer, I want to see balance on my accounts, so that I can make better informed decisions about my spending
</user-story-example>

This list of user stories should be extremely extensive and cover all aspects of the feature.

## Implementation Decisions

A list of implementation decisions that were made. This can include:

- The modules that will be built/modified
- The interfaces of those modules that will be modified
- Technical clarifications from the developer
- Architectural decisions
- Schema changes
- API contracts
- Specific interactions

Do NOT include specific file paths or code snippets. They may end up being outdated very quickly.

## Testing Decisions

A list of testing decisions that were made. Include:

- A description of what makes a good test (only test external behavior, not implementation details)
- Which modules will be tested
- Prior art for the tests (i.e. similar types of tests in the codebase)

## Out of Scope

A description of the things that are out of scope for this PRD.

## Further Notes

Any further notes about the feature.

More from this repository

same repository

zettelkasten

vinayprograms/agent-skills

Convert blogs and documentation sites into zettels for a zettelkasten repository using the `zet` MCP. Use when user wants to generate a zettel from a blog post link or an entire documentation site.

2026-07-090

grill-me

vinayprograms/agent-skills

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".

2026-05-150

to-tasks

vinayprograms/agent-skills

Break a plan, spec, or PRD into independently-grabbable tasks using tracer-bullet vertical slices. Use when user wants to convert a plan into tasks, create implementation tasks, or break down work into actionable items.

2026-05-150

go-engineering

vinayprograms/agent-skills

Go design and engineering guide covering idiomatic naming, interface-driven architecture, consumer-centric API design, error handling, concurrency, and testing. Use when writing new Go code, refactoring existing code, designing packages, reviewing APIs, or making architectural decisions. Also use when user says "write Go code", "design this package", "review this API", "refactor this", "make this idiomatic", or "clean up this Go code".

2026-04-110

brainstorm

vinayprograms/agent-skills

Balanced reasoning via parallel creative and critical analysis. Spawns both perspectives independently,

2026-04-110

## Problem Statement The problem that the user is facing, from the user's perspective. ## Solution The solution to the problem, from the user's perspective. ## User Stories A LONG, numbered list of user stories. Each user story should be in the format of: 1. As an <actor>, I want a <feature>, so that <benefit> <user-story-example> 1. As a mobile bank customer, I want to see balance on my accounts, so that I can make better informed decisions about my spending </user-story-example> This list of user stories should be extremely extensive and cover all aspects of the feature. ## Implementation Decisions A list of implementation decisions that were made. This can include: - The modules that will be built/modified - The interfaces of those modules that will be modified - Technical clarifications from the developer - Architectural decisions - Schema changes - API contracts - Specific interactions Do NOT include specific file paths or code snippets. They may end up being outdated very quickly. ## Testing Decisions A list of testing decisions that were made. Include: - A description of what makes a good test (only test external behavior, not implementation details) - Which modules will be tested - Prior art for the tests (i.e. similar types of tests in the codebase) ## Out of Scope A description of the things that are out of scope for this PRD. ## Further Notes Any further notes about the feature.