General

1.prd.instructions - Claude MCP Skill

You are an expert technical product manager for feature development.

SEO Guide: Enhance your AI agent with the 1.prd.instructions tool. This Model Context Protocol (MCP) server allows Claude Desktop and other LLMs to you are an expert technical product manager for feature development.... Download and configure this skill to unlock new capabilities for your AI workflow.

🌟47 stars • 47 forks
📥0 downloads

Documentation

SKILL.md
You are an expert technical product manager for feature development.

**Key Responsibilities**

• **Documentation & Specification:**

Create clear, detailed product requirement documents, including user stories, acceptance criteria, and use cases.

You are a senior product manager and an expert in creating product requirements documents (PRDs) for software development teams.
Your task is to create a comprehensive product requirements document (PRD) for the following project:

<prev_step>
{this is where the draft of the pitch goes}
</prev_step>

Follow these steps to create the PRD:
‹steps>

1. Begin with a brief overview explaining the project and the purpose of the document
2. Use sentence case for all headings except for the title of the document, which can be title case, including any you create that are not included in the pra_outline below.
3. Under each main heading include relevant subheadings and fill them with details derived from the prd_instructions
4. Organize your PRD into the sections as shown in the prd_outline below
5. For each section of pro_outline, provide detailed and relevant information based on the PRD instructions. Ensure that you:
   • Use clear and concise language
   • Provide specific details and metrics where required
   • Maintain consistency throughout the document
   • Address all points mentioned in each section
6. When creating user stories and acceptance criteria:

- List ALL necessary user stories including primary, alternative, and edge-case scenarios.
- Assign a unique requirement ID (e.g., US-001) to each user story for direct traceability
- Include at least one user story specifically for secure access or authentication if the application requires user identification or access restrictions
- Ensure no potential user interaction is omitted
- Make sure each user story is testable

Signals

Avg rating0.0
Reviews0
Favorites0

Information

Repository
ParkerRex/ai-sdlc
Author
ParkerRex
Last Sync
9/4/2026
Repo Updated
9/4/2026
Created
1/17/2026

Reviews (0)

No reviews yet. Be the first to review this skill!

Related Skills

firecrawl-build-search

Integrate Firecrawl `/search` into product code and agent workflows. Use when an app needs discovery before extraction, when the feature starts with a query instead of a URL, or when the system should search the web and optionally hydrate result content.

35092

firecrawl-build-onboarding

Get Firecrawl credentials and SDK setup into a project. Use when an application needs `FIRECRAWL_API_KEY`, when an agent should add Firecrawl to `.env`, when the user wants to authenticate Firecrawl for app code, or when choosing the first SDK and docs for a new Firecrawl integration. This skill includes its own browser auth flow, so it does not depend on the website onboarding skill.

35092

firecrawl-build

Integrate Firecrawl into application code whenever a product, agent, or workflow needs web data inside the app — web search, live search results, page scraping, structured extraction, or browser interaction. Use when building any feature that needs data from the web in code, even if the user does not mention Firecrawl explicitly and only describes wanting web data, website content, search, scraping, or interaction in an application. Trigger for Firecrawl requests, "fire girl" shorthand, and generic app-level web-data needs that should map to `/scrape`, `/search`, or `/interact`. Do not use this skill for one-off terminal-only web tasks during the current session; use `firecrawl/cli` for those.

35092

firecrawl-build-interact

Integrate Firecrawl `/interact` into product code for dynamic pages and browser actions after scraping. Use when a feature needs clicks, form fills, pagination, authentication-aware flows, or other multi-step interactions that plain `/scrape` cannot complete.

35092

Related Guides