Agent skill

pagent

Guide for using pagent - a PRD-to-code orchestration tool. Use when users ask how to use pagent, run agents, create PRDs, or transform requirements into code.

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill pagent-majiayu000-claude-skill-registr-84226916 --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 4 KB
Bundled scripts: none
Path: skills/agent/pagent-majiayu000-claude-skill-registr-84226916/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Pagent Usage Guide Pagent orchestrates specialist AI agents to transform Product Requirement Documents (PRDs) into working code. ## Quick Start ```bash # Interactive TUI (recommended) pagent ui # Run with a PRD file pagent run ./prd.md # Check agent status pagent status ``` ## Agents Pagent runs 5 specialist agents in dependency order: | Agent | Output | Purpose | |-------|--------|---------| | `architect` | `architecture.md` | Technical design, API specs, data models | | `qa` | `test-plan.md` | Test cases, acceptance criteria | | `security` | `security-assessment.md` | Threat model, security requirements | | `implementer` | `code/*` | Working code implementation | | `verifier` | `*_test.go`, `verification-report.md` | Tests and validation | ### Execution Order ``` Level 0: architect Level 1: qa, security (parallel) Level 2: implementer Level 3: verifier ``` ## Commands ### Run Agents ```bash # Run all agents (parallel by default) pagent run ./prd.md # Run specific agents pagent run ./prd.md --agents architect,qa # Sequential mode pagent run ./prd.md --sequential # Resume (skip up-to-date outputs) pagent run ./prd.md --resume # Force regeneration pagent run ./prd.md --force # Cus

What's inside
Steps it walks through
  1. Quick Start
  2. Agents
  3. Execution Order
  4. Commands
  5. Run Agents
  6. Interactive TUI
  7. Monitor & Control
  8. MCP Server
  9. Personas
  10. Configuration
  11. Writing a PRD
  12. Workflows
  13. Quick Architecture Review
  14. Full Pipeline
Ships with 1 file
  • metadata.json
Commands it runs
Interactive TUI (recommended)
pagent ui
Run with a PRD file
pagent run ./prd.md
Check agent status
pagent status
Run all agents (parallel by default)
Run specific agents
pagent run ./prd.md --agents architect,qa
Sequential mode
More from claude-skill-registry
All skills →
descriptive-statisticsSummarizing and visualizing data through measures of center, spread, shape, and position. Covers…Data & Analyticsperplexity-researcher-reasoning-proHighest level of research and reasoning capabilities for complex decision-making with significant…OtherretroBrutally honest engineering retrospective. Analyzes git history for what actually happened — not…Data & AnalyticsanalyzeUniversal multi-perspective analyzer for any topic, file, idea, or decision. Extract key points…Otherarize-prompt-optimizationINVOKE THIS SKILL when optimizing, improving, or debugging LLM prompts using production trace data…Data & Analyticscellxgene-contextGuide for integrating CellxGene Census single-cell data with ENCODE bulk experiments. Use when…Data & Analytics
About this skill
What does the pagent skill do?

Guide for using pagent - a PRD-to-code orchestration tool. Use when users ask how to use pagent, run agents, create PRDs, or transform requirements into code.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill pagent-majiayu000-claude-skill-registr-84226916 --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going
All skills →
The full catalog, by category and by tool.
Open Source Radar →
The repositories these skills come from, watched daily.
The people behind them →
Makers and builders across the ecosystem.