| description | FAQs and Troubleshooting Guide for Consolidated PRD Agent |
|---|---|
| phase | Phase 6 Rollout & Adoption |
| last_updated | 2026-09-12 |
- Getting Started
- Installation & Setup
- Using the Agent
- Provider-Specific Questions
- Troubleshooting
- Feedback & Support
The consolidated PRD Agent is a unified, production-ready tool for product requirement definition (PRD) and project planning. It consolidates 28 canonical skills into a single, maintainable agent that works seamlessly across three providers:
- Claude Code (native integration)
- GitHub Copilot (custom agent)
- OpenAI API (provider-agnostic definition)
Key Improvement: Single source of truth. Previously, PRD-related skills were scattered across 45+ folders with duplicated content. Now, all skills are in one canonical location with no redundancy.
Version: v2.3.0 (released 2026-09-12)
Test Status: ✅ 100% pass rate across all providers (14/14 tests per provider = 42/42 total)
Consolidated Benefits:
- Single Source of Truth: No confusion about which version to use. One canonical agent in
agents/prd-agent/. - Better Documentation: All 28 skills documented in one place with clear routing logic.
- Higher Quality: Extensively tested (100% test coverage, 3 providers, 14 tests each).
- Easier Maintenance: Bug fixes and improvements apply to all users automatically.
- Consistent Behavior: No version drift or hidden duplicate skills causing unexpected behavior.
Migration Path: Copy the appropriate agent definition to your repository:
- Claude Code users: Copy
agents/prd-agent/claude/agent.md - Copilot users: Copy
agents/prd-agent/copilot/agent.md - OpenAI API users: Use
agents/prd-agent/openai/agent.md
See Installation & Setup for step-by-step instructions.
The agent combines skills from five functional clusters:
1. Drafting & Requirements (4 skills)
prd-writer— Core PRD document creationacceptance-test-planner— Acceptance criteria and testingproject-intake— Project scoping and intake structuringproject-researcher— Research and context gathering
2. Planning & Strategy (6 skills)
implementation-plan-generator— Technical implementation roadmapsdelivery-planner— Timeline and task breakdownproject-status-reporter— Status reporting and metricsmemory-management— Knowledge and decision trackingapproval-gate-manager— Gate and checkpoint managementprd-agent-orchestrator— Multi-step workflow routing
3. Quality & Validation (5 skills)
prd-task-reviewer— PRD quality review and feedbackqa-findings-router— QA issue routing and triagevalidation-support— General validation and verificationmarkdown-content-validator— Document format validationevidence-locker— Evidence and artifact management
4. Coordination & Execution (5 skills)
change-request-router— Change management and routinglaunch-task-router— Launch readiness and handoffrelease-handoff-generator— Release coordinationproject-memory-manager— Team memory and contextprd-task-pack-exporter— Project export and packaging
5. Integration & Specialization (8 skills)
github-issue-drafter— GitHub issue integrationgithub-pr-workflow-guide— Pull request workflowsgithub-release-notes-generator— Release note automationgithub-milestone-tracker— Milestone managementlinear-issue-integration— Linear platform integrationgoogle-workspace-connector— Google Workspace collaborationplugin-architecture-guide— Plugin integration guidance- (Additional specialization skills as needed)
For detailed information on each skill, see instructions/AGENTS.md.
-
Clone or download the
agents/prd-agent/folder from the LightSpeed.githubrepository -
Copy
agents/prd-agent/claude/agent.mdinto your repository's.claude/agents/directory:mkdir -p .claude/agents cp agents/prd-agent/claude/agent.md .claude/agents/prd-agent.md
-
Restart Claude Code (if running)
-
In Claude Code, select "PRD Agent" from the agent dropdown menu
-
Start using the agent with your PRD workflows
Expected Behavior: Claude Code should recognize the YAML frontmatter and load the agent with correct name ("PRD Agent"), description, tools, and model.
-
Copy
agents/prd-agent/copilot/agent.mdinto your repository's.github/agents/directory:mkdir -p .github/agents cp agents/prd-agent/copilot/agent.md .github/agents/prd-agent.md
-
Commit and push the change
-
In GitHub Copilot settings, refresh the custom agents list
-
Select "PRD Agent" from the available custom agents
-
Start using the agent in Copilot chat or code generation workflows
Expected Behavior: Copilot should recognize the YAML frontmatter and load the agent with correct name, description, tools, and MCP servers.
- Use the agent definition at
agents/prd-agent/openai/agent.mdas a reference for your API calls - Extract the system prompt and integrate it into your OpenAI API client (e.g.,
gpt-4-turbo) - Configure the 28 skills as tool definitions in your OpenAI function calling setup
- Call the OpenAI API with your custom system prompt and skill tools
Expected Behavior: API calls should work with the provided prompt and skill routing logic.
See Troubleshooting: Agent Won't Load.
Short Answer: Most workflows continue without changes, but verify skill-routing mappings for custom identifiers.
Changes to Expect:
- Identical skill capabilities (28 consolidated skills provide all previous functionality)
- Same agent interface (Claude Code, Copilot, OpenAI remain unchanged)
- Improved response quality (100% test coverage means higher reliability)
- Better error handling (consolidated skills route more intelligently)
Skill Routing Mappings (verify these continue working):
prd_create→ consolidated PRD creation skillprd_validate→ consolidated PRD validation skillsprint_planner→ consolidated sprint planning skill
Migration Guidance: If your workflows reference these identifiers explicitly, the consolidated agent preserves these mappings. If you use the agent through high-level workflows without explicit skill calls, no changes needed. Review your workflow integration points if you have custom orchestration.
The consolidated agent supports the full PRD lifecycle:
1. PRD Creation
- Draft new PRDs from project scope and requirements
- Generate acceptance criteria and testing strategies
- Create implementation roadmaps and timelines
2. PRD Review & Quality
- Review PRDs for clarity, completeness, and feasibility
- Identify gaps and suggest improvements
- Validate against quality standards
3. Change Management
- Route and manage PRD changes and updates
- Track change history and impact analysis
- Update related workflows (timelines, implementation plans)
4. Coordination & Handoff
- Generate launch readiness checklists
- Create release notes and deployment guides
- Manage team approval gates and sign-offs
5. Integration & Reporting
- Export projects as packaged deliverables
- Generate status reports and metrics
- Integrate with GitHub, Linear, Google Workspace
See instructions/AGENTS.md for detailed skill routing and workflow examples.
The agent's orchestrator skill (prd-agent-orchestrator) automatically routes requests to the appropriate skill. You generally don't need to specify a skill explicitly.
Examples of Automatic Routing:
-
"Write a PRD for a user preferences panel" → Routes to
prd-writer(drafting cluster) -
"Review this PRD for clarity and completeness" → Routes to
prd-task-reviewer(quality cluster) -
"Generate a launch checklist for this project" → Routes to
launch-task-router(coordination cluster) -
"Create GitHub issues from this PRD" → Routes to
github-issue-drafter(integration cluster)
If You Need Specific Skill Help: You can explicitly mention a skill name in your request. The agent will recognize it and route accordingly. See instructions/AGENTS.md for the full routing table.
Typical Duration: 3-10 minutes depending on project complexity and amount of research required.
Factors:
- Project Complexity: Simple projects (feature tweaks) = 3-5 min. Complex projects (new platform) = 10-20 min.
- Input Quality: Well-scoped requirements = faster. Vague or incomplete input = slower (agent may ask clarifying questions).
- Research Needed: Projects requiring external research (competitor analysis, technical specs) = longer.
Optimization Tips:
- Provide clear, detailed project scope upfront
- Include acceptance criteria or user stories if available
- Specify any constraints (timeline, technical limitations, dependencies)
- Ask for structured output (JSON, YAML, markdown) to reduce formatting time
Claude Code (Recommended for PRD Work)
- ✅ Better at long-form content generation (PRDs are typically 1000+ words)
- ✅ Stronger context management (handles complex project scopes)
- ✅ Preferred for deep PRD work (design, validation, iteration)
- ✅ Direct integration: Copy agent file, use immediately
GitHub Copilot
- ✅ Better integration with GitHub workflows (issues, PRs, discussions)
- ✅ Lighter weight: Good for quick PRD sketches or outlines
- ✅ Seamless in GitHub web UI
⚠️ May truncate very long PRD documents (edge case)
Recommendation: Use Claude Code for primary PRD work; use Copilot for GitHub-specific integration tasks (creating issues, drafting release notes).
Native Integrations (via skills):
- ✅ GitHub: Issue creation, PR workflows, release notes, milestones
- ✅ Linear: Issue creation, project linking, status updates
- ✅ Google Workspace: Doc sharing, calendar integration, meeting notes
Indirect Support (via manual export):
⚠️ Jira: Export PRD as JSON/YAML, import manually into Jira⚠️ Asana: Export PRD as structured data, import as Asana tasks⚠️ Slack: Export PRD, share in Slack (no direct bot integration)
To Request New Integrations: Open a GitHub issue tagged [INTEGRATION-REQUEST] with details on the tool and integration use case.
Consolidated Agent (agents/prd-agent/)
- ✅ Portable: Works in any LightSpeedWP repository
- ✅ Well-tested: 100% test pass rate, 3 providers
- ✅ Actively maintained: Phase 6+ updates
- ✅ Recommended: Use this going forward
Spec-Based Agent (agents/mode-prd.agent.md in .github control plane)
⚠️ GitHub-specific: Only works in.githubrepository⚠️ Legacy: May become archived after Phase 7 decision- ❌ Not recommended for new projects
Recommendation: Use the consolidated agent. The spec-based agent will be archived or synced to consolidated version after Phase 6 adoption metrics are collected (Phase 7 decision).
Problem: Agent file copied, but Claude Code/Copilot doesn't recognize it.
Diagnosis:
-
Check file location:
- Claude Code:
.claude/agents/prd-agent.md✅ - Copilot:
.github/agents/prd-agent.md✅ - Other: Verify path matches your provider's agent directory
- Claude Code:
-
Check YAML frontmatter:
- Confirm file starts with
---followed by valid YAML (no syntax errors) - Required fields:
name,description,model(Claude) ormcp-servers(Copilot)
- Confirm file starts with
-
Restart IDE:
- Close and reopen your editor
- In VS Code: Reload window (
Ctrl+Shift+P→ "Reload Window")
Solution Steps:
- Verify file location and YAML syntax
- Restart IDE
- Check provider logs (Claude Code:
.claude/logs/; Copilot: Extension output panel) - If still failing, share the error message in
#product-planningSlack or open a GitHub issue
Problem: Agent loads, but responses are off-topic or incomplete.
Diagnosis:
-
Check your request clarity:
- Vague: "Write a PRD" → Too open-ended
- Clear: "Write a PRD for a user preferences panel (3-5 pages, includes acceptance criteria)"
-
Check prompt version:
- Ensure you're using v2.3.0 (check agent file creation date: 2026-09-12 or later)
- Old versions (v2.0.0, v2.1.0) have weaker skill routing
-
Check for provider limitations:
- Claude Code: Should handle any PRD task
- Copilot: May truncate very long outputs (>4000 tokens)
- OpenAI API: Depends on your model (use gpt-4-turbo or newer)
Solution Steps:
- Provide clear, detailed project scope
- Update to v2.3.0 if using older version
- Try Claude Code if using Copilot (rule out provider limitation)
- If issue persists, open GitHub issue with example request and response
Problem: Agent takes >10 minutes to generate a PRD.
Diagnosis:
-
Check request complexity:
- Complex projects (enterprise platform, lots of research needed) = slower
- Simple projects (feature tweak) = should be <5 min
-
Check provider load:
- Claude Code: Usually fast; check if running many concurrent tasks
- Copilot: May be slower during peak GitHub usage
- OpenAI API: Depends on API queue and rate limits
-
Check for infinite loops:
- Agent asking clarifying questions → Answering incompletely → Asking again
- Should terminate after 2-3 clarification rounds
Solution Steps:
- Provide complete input upfront (reduce clarification rounds)
- Break large projects into smaller PRDs (1 skill area per PRD)
- Check provider status/docs for known slowdowns
- If stuck in loop: Interrupt and restart with clearer scope
Problem: Agent routes to wrong skill (e.g., asks for PRD when you asked for review).
Diagnosis:
-
Check request clarity:
- Request should explicitly mention the task type (draft, review, plan, etc.)
- Example: "Review this PRD for clarity" vs. ambiguous "Improve this PRD"
-
Check if skill exists:
- Not all 28 skills are equally active in all versions
- Some skills may be in beta or limited availability
-
Check for ambiguous requests:
- Multi-step requests may be broken down incorrectly
- Example: "Write and review this PRD" → Single step preferred
Solution Steps:
- Rephrase request to be clearer about task type
- Break multi-step requests into separate agent invocations
- Explicitly mention skill name if known (e.g., "Use the prd-task-reviewer skill to review this")
- Open GitHub issue if routing consistently wrong for a specific task type
Problem: Agent outputs JSON when you asked for Markdown, or format doesn't match your needs.
Diagnosis:
-
Check output request:
- Did you specify format? ("as markdown", "as JSON", "as a table")
- Agent defaults to markdown for PRDs, JSON for data exports
-
Check for parsing issues:
- If output looks corrupted, may be truncation or encoding issue
- Try requesting specific section instead of full output
Solution Steps:
- Specify output format explicitly: "Output this as [format]"
- Request smaller chunks if truncation suspected
- Copy/paste output and share in issue if format corrupted
Problem: Agent claims a skill is unavailable, but you see it in documentation.
Diagnosis:
-
Check skill name spelling:
- Skill names use hyphens, not underscores (e.g.,
prd-writer, notprd_writer) - Check
instructions/AGENTS.mdfor exact names
- Skill names use hyphens, not underscores (e.g.,
-
Check agent version:
- Older agent versions (v2.0.0, v2.1.0) have fewer skills
- Ensure using v2.3.0 (all 28 skills available)
-
Check provider availability:
- Some skills may be provider-specific (e.g., GitHub integration only in Copilot)
Solution Steps:
- Verify skill name spelling against
instructions/AGENTS.md - Update to v2.3.0 if using older version
- Try a different provider if skill unavailable
- Open issue if skill should be available but isn't
How to Report:
-
Document the issue:
- What you asked the agent to do
- What it should have done (expected behavior)
- What it actually did (actual behavior)
- Any error messages or logs
-
Open a GitHub issue with label
[ROLLOUT-FEEDBACK]:- Title: Brief description of bug
- Body: Include steps to reproduce, expected vs. actual behavior
- Severity:
critical/high/medium/low
-
If critical (blocks usage):
- Post in
#product-planningSlack immediately - Contact Ash Shaw for urgent escalation
- Post in
Examples of What to Include:
Title: PRD writer skill truncates long acceptance criteria
Steps to reproduce:
1. Ask agent: "Write a PRD with 20+ acceptance criteria"
2. Agent generates PRD with only first 10 criteria
Expected: All 20+ criteria included in output
Actual: Only 10 criteria shown; rest are truncated
Provider: Claude Code v2.3.0
Request: [paste your exact request]
Output: [paste the generated PRD - redact sensitive data]
For Bugs or Critical Issues:
- Slack:
#product-planningchannel or DM Ash Shaw - GitHub: Open issue with label
[ROLLOUT-FEEDBACK]+ severity label
For Feature Requests:
- GitHub: Open issue with label
[FEATURE-REQUEST] - Include: What feature, why needed, example use case
For Questions or Help:
- Slack: Ask in
#product-planning - Email: Contact Ash Shaw (ash@lightspeedwp.agency)
- This FAQ: Check if your question is covered above
| Document | Purpose |
|---|---|
| README.md | Overview of agent and quick-start |
| instructions/AGENTS.md | Detailed skill routing and workflow examples |
| ROLLOUT_PLAN.md | Rollout strategy and timeline |
| ADOPTION_METRICS.md | Metrics framework for measuring success |
| TEST_RESULTS.md | Phase 5 testing results (100% pass rate baseline) |
| CHANGELOG.md | Version history and release notes |
All documents are located in agents/prd-agent/ folder.
Yes! The consolidated PRD agent is maintained and improved based on team feedback.
How to Contribute:
- Report issues or feature requests (see above)
- Suggest improvements for skill routing or documentation
- Share success stories or use cases (helps with adoption)
- Participate in Phase 6 feedback (surveys, team briefings)
Process:
- Feature requests → Evaluated for Phase 6+ roadmap
- Bug reports → Triaged by severity; critical bugs fixed immediately
- Documentation improvements → Accepted via PR to agents/prd-agent/
Contact: Ash Shaw (ash@lightspeedwp.agency) or open GitHub issue
| Provider | File Path | Load Via |
|---|---|---|
| Claude Code | agents/prd-agent/claude/agent.md |
.claude/agents/ directory |
| Copilot | agents/prd-agent/copilot/agent.md |
.github/agents/ directory |
| OpenAI API | agents/prd-agent/openai/agent.md |
System prompt + function calls |
| Channel | Purpose |
|---|---|
#product-planning |
Agent discussions, feedback, support |
#engineering |
Technical integration questions |
#general |
Announcements and org-wide updates |
- Consolidated Agent:
agents/prd-agent/(LightSpeed.githubrepository) - Issue Tracker: GitHub Issues (label:
[ROLLOUT-FEEDBACK]) - Feedback Form (Phase 6): Google Form link (distributed Week 4)
- Adoption Metrics:
agents/prd-agent/ADOPTION_METRICS.md
| Date | Author | Change |
|---|---|---|
| 2026-09-12 | Claude Haiku 4.5 | Initial FAQ created; Phase 6 FR-605 implemented |
Still have questions? Open a GitHub issue or post in #product-planning Slack. We're here to help! 🚀
Maintained with ❤️ by the 🚀 LightSpeedWP Automation Team Org Profile
Maintained with ❤️ by the 🚀 LightSpeedWP Automation Team Org Profile
Maintained with ❤️ by the 🚀 LightSpeedWP Automation Team Org Profile
Maintained with ❤️ by the 🚀 LightSpeedWP Automation Team Org Profile
Maintained with ❤️ by the 🚀 LightSpeedWP Automation Team Org Profile
Maintained with ❤️ by the 🚀 LightSpeedWP Automation Team Org Profile
Maintained with ❤️ by the 🚀 LightSpeedWP Automation Team Org Profile
Maintained with ❤️ by the 🚀 LightSpeedWP Automation Team Org Profile
Maintained with ❤️ by the 🚀 LightSpeedWP Automation Team Org Profile
Maintained with ❤️ by the 🚀 LightSpeedWP Automation Team Org Profile
Maintained with ❤️ by the 🚀 LightSpeedWP Automation Team Org Profile
Maintained with ❤️ by the 🚀 LightSpeedWP Automation Team Org Profile
Maintained with ❤️ by the 🚀 LightSpeedWP Automation Team Org Profile
Maintained with ❤️ by the 🚀 LightSpeedWP Automation Team Org Profile
Maintained with ❤️ by the 🚀 LightSpeedWP Automation Team Org Profile
Maintained with ❤️ by the 🚀 LightSpeedWP Automation Team Org Profile
Maintained with ❤️ by the 🚀 LightSpeedWP Automation Team Org Profile
Maintained with ❤️ by the 🚀 LightSpeedWP Automation Team Org Profile