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.

🌟45 stars • 50 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
5/11/2026
Repo Updated
5/6/2026
Created
1/17/2026

Reviews (0)

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

Related Skills

browser-use

Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, or extract information from web pages.

23311

cloud

Documentation reference for using Browser Use Cloud — the hosted API and SDK for browser automation. Use this skill whenever the user needs help with the Cloud REST API (v2 or v3), browser-use-sdk (Python or TypeScript), X-Browser-Use-API-Key authentication, cloud sessions, browser profiles, profile sync, CDP WebSocket connections, stealth browsers, residential proxies, CAPTCHA handling, webhooks, workspaces, skills marketplace, liveUrl streaming, pricing, or integration patterns (chat UI, subagent, adding browser tools to existing agents). Also trigger for questions about n8n/Make/Zapier integration, Playwright/ Puppeteer/Selenium on cloud infrastructure, or 1Password vault integration. Do NOT use this for the open-source Python library (Agent, Browser, Tools config) — use the open-source skill instead.

23311

agent-builder

Design and build AI agents for any domain. Use when users: (1) ask to "create an agent", "build an assistant", or "design an AI system" (2) want to understand agent architecture, agentic patterns, or autonomous AI (3) need help with capabilities, subagents, planning, or skill mechanisms (4) ask about Claude Code, Cursor, or similar agent internals (5) want to build agents for business, research, creative, or operational tasks Keywords: agent, assistant, autonomous, workflow, tool use, multi-step, orchestration

14924

mem0-integrate

Integrate Mem0 into an existing repository using a goal-driven, TDD pipeline. Detects the repo's language automatically and asks the user to pick between Mem0 Platform (managed) and Mem0 Open Source (self-hosted). Writes failing tests before any implementation. Produces a local feature branch plus `.mem0-integration/` artifacts consumed by the paired verification skill. TRIGGER when: user says "integrate mem0", "add mem0 to this repo", "wire mem0 into <repo>", or asks how to add memory to an existing project. DO NOT TRIGGER when: the user wants general SDK usage (use skill:mem0), CLI usage (use skill:mem0-cli), or Vercel AI SDK (use skill:mem0-vercel-ai-sdk). After success, invoke skill:mem0-test-integration to verify in the same workspace (loose coupling).

11064

Related Guides