Run any Skill in Manus with one click

to-prd

Stars6

Forks0

UpdatedJune 3, 2026 at 14:18

Turn conversation context into a VFloat PRD in .scratch for the AFK issue workflow. Use when creating a PRD, feature brief, or parent planning file that will later be broken into issue-worker tasks.

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

sherif414

sherif414/VFloat

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

SKILL.md

readonly

name	to-prd
description	Turn conversation context into a VFloat PRD in .scratch for the AFK issue workflow. Use when creating a PRD, feature brief, or parent planning file that will later be broken into issue-worker tasks.

To PRD

This skill synthesizes the current conversation and codebase understanding into a PRD file for the local markdown issue tracker. Do not interview the user unless a product decision is genuinely missing.

Workflow Integration

Read before writing:

AGENTS.md
.agents/workflows/afk-issue-loop.md
.agents/issue-tracker.md
.agents/triage-labels.md
CONTEXT.md and relevant ADRs, if present

The PRD should be ready for to-issues to split into independently grabbable AFK issues. It should not assume Codex-only tooling.

Process

Explore the repo enough to describe the current state accurately. Use the project's domain glossary vocabulary and respect relevant ADRs.
Identify the major modules or public interfaces likely to change. Prefer behavioral contracts over file paths.
Look for deep modules that can be tested in isolation, but keep the PRD at the product and architectural decision level.
Write .scratch/<feature-slug>/PRD.md using the template below.
Set Status: needs-triage unless the user explicitly says the plan is already approved for issue breakdown.

PRD Template

Status: needs-triage
Category: enhancement

# <Feature Title>

## Problem Statement

The problem from the user's perspective.

## Solution

The intended solution from the user's perspective.

## User Stories

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

## Implementation Decisions

- Durable decisions about behavior, contracts, modules, or architecture.
- Avoid brittle file paths and line numbers.

## Testing Decisions

- Behaviors that need regression coverage.
- Existing test patterns or seams to reuse.
- Validation expectations for downstream issues.

## Out of Scope

- Related work that should not be included.

## Further Notes

- Context useful for `to-issues`, `triage`, workers, reviewers, or committers.

Handoff

After publishing, tell the user the PRD path and that to-issues is the next skill for breaking it into AFK-ready vertical slices.

More from this repository

same repository

documentation-writer

sherif414/VFloat

Use this skill when creating, updating, reviewing, or syncing VFloat documentation in docs/api or docs/guide, especially after source changes in src/composables/ or when the user asks for VFloat API pages, guides, tutorials, doc fixes, or docs review feedback even if they do not name the docs folders directly.

2026-06-046

agent-workflow

sherif414/VFloat

Coordinate VFloat's markdown-based AFK issue workflow. Use when creating, assigning, implementing, reviewing, committing, or monitoring .scratch PRD and issue files across Codex or other markdown-capable agents.

2026-06-036

diagnose

sherif414/VFloat

Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.

2026-06-036

improve-codebase-architecture

sherif414/VFloat

Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.

2026-06-036

issue-committer

sherif414/VFloat

Prepare final validation and Conventional Commit proposals for completed VFloat AFK workflow work. Use when all feature issues are completed or a PRD is ready-to-commit.

2026-06-036

issue-reviewer

sherif414/VFloat

Review one VFloat AFK workflow issue after implementation. Use when an issue is ready-for-review and needs diff review, acceptance validation, follow-up issue creation, or completion.

2026-06-036

To PRD

Workflow Integration

Read before writing:

AGENTS.md

.agents/workflows/afk-issue-loop.md

.agents/issue-tracker.md

.agents/triage-labels.md

CONTEXT.md and relevant ADRs, if present

The PRD should be ready for to-issues to split into independently grabbable AFK issues. It should not assume Codex-only tooling.

Process

Explore the repo enough to describe the current state accurately. Use the project's domain glossary vocabulary and respect relevant ADRs.

Identify the major modules or public interfaces likely to change. Prefer behavioral contracts over file paths.

Look for deep modules that can be tested in isolation, but keep the PRD at the product and architectural decision level.

Write .scratch/<feature-slug>/PRD.md using the template below.

Set Status: needs-triage unless the user explicitly says the plan is already approved for issue breakdown.

PRD Template

Status: needs-triage Category: enhancement # <Feature Title> ## Problem Statement The problem from the user's perspective. ## Solution The intended solution from the user's perspective. ## User Stories 1. As an <actor>, I want <feature>, so that <benefit>. ## Implementation Decisions - Durable decisions about behavior, contracts, modules, or architecture. - Avoid brittle file paths and line numbers. ## Testing Decisions - Behaviors that need regression coverage. - Existing test patterns or seams to reuse. - Validation expectations for downstream issues. ## Out of Scope - Related work that should not be included. ## Further Notes - Context useful for `to-issues`, `triage`, workers, reviewers, or committers.

Handoff

After publishing, tell the user the PRD path and that to-issues is the next skill for breaking it into AFK-ready vertical slices.