메뉴
Main entry Skill for PRD-Driven Development, orchestrating the entire development process. Invoke this Skill when users want to develop features based on PRD documents. 支持中文触发：PRD驱动开发、基于PRD开发、PDD开发、功能开发、PRD开发。
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | pdd-main |
| description | Main entry Skill for PRD-Driven Development, orchestrating the entire development process. Invoke this Skill when users want to develop features based on PRD documents. 支持中文触发：PRD驱动开发、基于PRD开发、PDD开发、功能开发、PRD开发。 |
| license | MIT |
| compatibility | Requires complete PRD document system |
| metadata | {"author":"neuqik@hotmail.com","version":"3.2"} |
Core Concept: PDD (PRD-Driven Development) is a development methodology that combines domain expert capabilities. By integrating system-architect, software-architect, software-engineer, and expert-xxx skills, it achieves comprehensive intelligence from requirement analysis to final delivery.
Input: PRD document directory path
Output: Completed feature code and verification report
| Version | Date | Changes |
|---|---|---|
| 3.4 | 2026-03-22 | Added PDD implementation specification reference, updated skill collaboration process |
| 3.3 | 2026-03-21 | Fixed code directory generation rules: new business features create independent Maven modules, not in asset-system |
| 3.2 | 2026-03-21 | Added automatic code directory generation capability (module number → code path mapping) |
| 3.1 | 2026-03-21 | Added intelligent PRD discovery capability (module number auto-discovery + manual document specification) |
| 3.0 | 2026-03-21 | Integrated system-architect, software-architect, software-engineer skills |
| 2.0 | 2026-03-08 | Rined four-phase process, enhanced verification mechanism |
| 1.0 | Early | Initial version |
┌─────────────────────────────────────────────────────────────────┐
│ PDD-MAIN (Main Entry) │
│ ┌─────────────┬─────────────┬─────────────┬─────────────┐ │
│ │ Process │ State │ Context │ Result │ │
│ │ Orchestration│ Management │ Transfer │ Aggregation │ │
│ └─────────────┴─────────────┴─────────────┴─────────────┘ │
└─────────────────────────────────────────────────────────────────┘
│
┌─────────────────────┼─────────────────────┐
│ │ │
▼ ▼ ▼
┌───────────────┐ ┌───────────────┐ ┌───────────────┐
│ PDD Process │ │ Architect │ │ Engineer │
│ Layer │ │ Layer │ │ Layer │
├───────────────┤ ├───────────────┤ ├───────────────┤
│ pdd-ba │ │system-architect│ │software-eng │
│ pdd-extract │◄───►│ │◄───►│ │
│ pdd-generate │ │software-arch │ │ expert-xxx │
│ pdd-implement │ │ │ │ │
│ pdd-review │ │ │ │ │
│ pdd-verify │ │ │ │ │
└───────────────┘ └───────────────┘ └───────────────┘
| Category | Skill Name | Core Responsibility | Capability Boundary |
|---|---|---|---|
| Main Entry | pdd-main | Process orchestration, state management, context transfer | Does not directly implement code |
| PDD Process | pdd-ba, pdd-extract-features, pdd-generate-spec, pdd-implement-feature, pdd-code-reviewer, pdd-verify-feature | Business analysis, specification generation, code implementation, review verification | Each responsible for specific phase |
| Architect | system-architect | System architecture design, technology selection | High-level design, architecture decisions |
| software-architect | Software architecture design, module division | Module design, interface specification | |
| Engineer | software-engineer | Code implementation, test writing | Execute implementation based on specification |
| Expert | expert-ruoyi | RuoYi framework specific issues | Framework configuration, code generation |
| expert-activiti | Activiti workflow engine | BPMN design, process deployment | |
| expert-mysql | MySQL database optimization | SQL optimization, index design | |
| expert-code-quality | Code quality and refactoring | Smell detection, design patterns |
Phase 1: Business Analysis and Feature Extraction
PRD Document → 5W1H Analysis → Use Case Diagram → Flowchart → State Diagram → Feature Matrix
Phase 2: Development Specification Generation
Feature Matrix → Architecture Consultation → Interface Design → Data Model → Dev Spec + Acceptance Criteria
Phase 3: Feature Loop
For each feature: Implementation → Review → Fix → Acceptance
Phase 4: Architecture Review Integration
On-demand system-architect / software-architect invocation
Phase 5: Expert Skills Integration
On-demand expert-xxx invocation
Phase 6: Delivery and Retrospective
Development Report → Document Archival → Lessons Learned
Two Input Modes Supported:
Mode A: Module Number Auto-Discovery
ZCCZ-2, ZCCZ-1)docs/business-analysis/ directoryZCCZ-2-Asset-Transfer)Mode B: Manual Document Specification
docs/xxx/ZCCZ-2/PRD-Asset-Transfer.mdStandard PRD Document Structure:
docs/business-analysis/{business-domain}/
├── PRD-{module-name}.md # Requirements document
├── UseCase-{module-name}.md # Use case diagram
├── BusinessFlow-{module-name}.md # Flowchart
├── StateDiagram-{module-name}.md # State diagram
├── SequenceDiagram-{module-name}.md # Sequence diagram (optional)
└── FormDesign/ # Form design documents (optional)
Auto-Discovery Process:
User Input: "ZCCZ-2"
↓
Scan docs/business-analysis/*/ZCCZ-2*/
↓
Match: docs/business-analysis/asset-disposition/ZCCZ-2-Asset-Transfer/
↓
Aggregate Documents:
- PRD-Asset-Transfer.md
- UseCase-Asset-Transfer.md
- BusinessFlow-Asset-Transfer.md
- StateDiagram-Asset-Transfer.md
- SequenceDiagram-Asset-Transfer-Process.md
↓
Confirm Document Completeness
Extract module number and name from PRD document:
Analyze project technology stack, determine which skills to invoke:
Invoke pdd-ba skill:
Invoke pdd-extract-features skill:
Wait for user to review feature matrix:
Invoke pdd-generate-spec skill:
Architecture Consultation (On-Demand):
system-architect: Technology selection, system architecturesoftware-architect: Module division, interface designWait for user to review development specification:
Automatically generate code directory that conforms to standards based on module number and functionality.
⚠️ Important Principles:
asset-systemasset-system is the system management module, only contains system-related code (users, roles, menus, etc.)asset-{business-domain} (e.g., asset-disposition, asset-equity)Module Number to Code Path Mapping:
| Module Number | Feature Name | Maven Module | Backend Package Path | Frontend Path |
|---|---|---|---|---|
| ZCCZ-1 | Equity Transfer | asset-equity | com.example.equity.transfer | equity-transfer |
| ZCCZ-2 | Asset Transfer | asset-equity | com.example.equity.transfer | asset-transfer |
| ZCCZ-3 | Enterprise Capital Increase | asset-equity | com.example.equity.capital | capital-increase |
| ZCCZ-4 | Equity Free Allocation | asset-equity | com.example.equity.allocation | equity-allocation |
| ZCCZ-5 | Asset Lease | asset-lease | com.example.lease | asset-lease |
| ZCCZ-6 | Enterprise Guarantee | asset-guarantee | com.example.guarantee | enterprise-guarantee |
| ZCCZ-7 | Fixed Asset Disposal | asset-disposition | com.example.disposition | fixed-asset-scrap |
Backend Module Directory Structure:
asset-{business-domain}/ # Independent Maven module
├── pom.xml
└── src/
├── main/
│ ├── java/
│ │ └── com/example/{module}/
│ │ ├── controller/ # Controllers
│ │ ├── domain/ # Entity classes
│ │ │ └── vo/ # VO objects
│ │ ├── mapper/ # Mapper interfaces
│ │ ├── service/ # Service interfaces
│ │ │ └── impl/ # Service implementations
│ │ ├── constant/ # Constant classes
│ │ └── util/ # Utility classes
│ └── resources/
│ └── mapper/
│ └── {module}/ # Mapper XML
└── test/
└── java/
└── com/example/{module}/ # Test classes
Frontend Directory Structure:
asset-ui/src/
├── api/
│ └── {module}/ # API interfaces
│ └── {feature}.js
└── views/
└── {module}/ # View pages (camelCase)
├── index.vue # List page
├── form.vue # Form page
└── detail.vue # Detail page
Example: ZCCZ-1 Equity Transfer
Backend:
asset-equity/ # Create independent module
├── pom.xml
└── src/main/java/com/example/equity/transfer/
├── controller/
│ └── EquityTransferApplyController.java
├── domain/
│ ├── EquityTransferApply.java
│ └── vo/
├── mapper/
├── service/
│ └── impl/
└── constant/
└── src/main/resources/mapper/equity/transfer/
Frontend:
asset-ui/src/api/equity/transfer.js
asset-ui/src/views/equity-transfer/
├── index.vue
├── form.vue
└── detail.vue
Existing Module Reuse Rules:
| Existing Module | Applicable Business | Description |
|---|---|---|
| asset-disposition | Asset disposal type | Fixed asset disposal, asset write-off, etc. (already exists) |
| asset-equity | Equity transaction type | Equity transfer, enterprise capital increase, etc. (needs to be created) |
| asset-admin | System management | Controller entry, configuration, etc. |
| asset-system | System functions | Users, roles, menus, etc. (do not put business code) |
Error Examples (To Avoid):
❌ Wrong: Put business code in asset-system
asset-system/src/main/java/com/example/equity/ # Wrong!
✅ Correct: Create independent business module
asset-equity/src/main/java/com/example/equity/ # Correct!
For each feature (by priority P0 → P1 → P2):
a. Invoke Feature Implementation
pdd-implement-feature skillb. Invoke Software Engineer
software-engineer skillc. Expert Consultation (On-Demand)
expert-ruoyiexpert-mysqlexpert-code-qualityd. Invoke Code Review
pdd-code-reviewer skille. Architecture Review (On-Demand)
software-architectsystem-architectf. Handle Review Results
g. Invoke Feature Verification
pdd-verify-feature skillh. Handle Acceptance Results
Generate final development report
Trigger Conditions:
Service Content:
Trigger Conditions:
Service Content:
Trigger Conditions:
Service Content:
| Expert Skill | Trigger Condition | Expected Output |
|---|---|---|
| expert-ruoyi | RuoYi framework issues | Solution + Best practices |
| expert-activiti | Workflow issues | BPMN design recommendations |
| expert-mysql | Database issues | SQL optimization plan |
| expert-code-quality | Code quality issues | Refactoring plan |
Automatically select AI role based on feature complexity:
| Complexity | AI Role | Human Involvement | Applicable Scenarios |
|---|---|---|---|
| P0 | Collaborator + Architect + Expert | High | Core business processes, complex state transitions |
| P1 | Collaborator + Architect | Medium | Important features, medium complexity |
| P2 | Leader + Engineer | Low | Simple features, auxiliary features |
P0 (Core Business):
pdd-main + pdd-ba + pdd-generate-spec
↓ Architecture consultation
system-architect + software-architect
↓
pdd-implement-feature + software-engineer
↓ + expert-ruoyi + expert-mysql
pdd-code-reviewer + software-architect
↓
pdd-verify-feature
P1 (Important Features):
pdd-main + pdd-extract + pdd-generate-spec
↓ On-demand consultation
software-architect (if needed)
↓
pdd-implement-feature + software-engineer
↓ + expert-xxx (on-demand)
pdd-code-reviewer
↓
pdd-verify-feature
P2 (Auxiliary Features):
pdd-main + pdd-generate-spec
↓
pdd-implement-feature + software-engineer (lead)
↓
pdd-code-reviewer (simplified)
↓
pdd-verify-feature
| Skill Name | Description | Input | Output | Trigger Timing |
|---|---|---|---|---|
| pdd-ba | Business analysis, using professional methodologies for requirement derivation | PRD document path | Business analysis report | At process start |
| pdd-extract-features | Extract feature matrix from PRD | PRD document path | feature-matrix.md | After business analysis |
| pdd-generate-spec | Generate development specification | Feature matrix | spec.md, checklist.md | After feature confirmation |
| pdd-implement-feature | Implement feature code | Development specification | Code files | After specification confirmation |
| pdd-code-reviewer | Code review, verify implementation conforms to specification | Code + Specification | Review report | After code implementation |
| pdd-verify-feature | Verify feature implementation | Code + Acceptance criteria | Acceptance report | After code review |
| pdd-doc-change | Document change management | Change requirements | Updated documents | When requirements change |
| system-architect | System architecture consultation | Architecture requirements | Architecture plan | On-demand trigger |
| software-architect | Software architecture consultation | Module requirements | Module design | On-demand trigger |
| software-engineer | Code implementation and testing | Specification document | Code files | Implementation phase |
| expert-ruoyi | RuoYi framework expert consultation | Technical issues | Solution | On-demand trigger |
| expert-activiti | Activiti workflow expert | Process issues | Solution | On-demand trigger |
| expert-mysql | MySQL database expert | SQL/structure issues | Optimization recommendations | On-demand trigger |
| expert-code-quality | Code quality expert | Code snippets | Refactoring plan | On-demand trigger |
┌─────────────────────────────────────────────────────────────────┐
│ PDD-MAIN Main Process │
├─────────────────────────────────────────────────────────────────┤
│ │
│ PRD Document ──→ pdd-ba ──→ Business Analysis Report │
│ │ │
│ ↓ │
│ pdd-extract-features ──→ Feature Matrix │
│ │ │
│ ↓ │
│ [Manual Review] │
│ │ │
│ ↓ │
│ pdd-generate-spec ──→ Dev Spec + Acceptance Criteria │
│ │ │
│ ├────── (on-demand) ──→ system-architect │
│ │ │
│ ├────── (on-demand) ──→ software-architect │
│ │ │
│ ↓ │
│ [Manual Review] │
│ │ │
│ ↓ │
│ ┌──────────────────────────────────────┐ │
│ │ Feature Loop Processing │ │
│ │ ┌────────────────────────────────┐ │ │
│ │ │ pdd-implement-feature │ │ │
│ │ │ ↓ │ │ │
│ │ │ software-engineer │ │ │
│ │ │ ↓ (on-demand) │ │ │
│ │ │ expert-ruoyi / expert-mysql │ │ │
│ │ │ ↓ │ │ │
│ │ │ pdd-code-reviewer │ │ │
│ │ │ ↓ (on-demand) │ │ │
│ │ │ software-architect │ │ │
│ │ │ ↓ │ │ │
│ │ │ [Critical issues?] ─→ Fix ─┐ │ │ │
│ │ │ ↓ (none) │ │ │ │
│ │ │ pdd-verify-feature │ │ │ │
│ │ │ ↓ │ │ │ │
│ │ │ [Passed?] ─→ Next feature │ │ │ │
│ │ │ ↓ (not passed) │ │ │ │
│ │ │ Re-develop ←───────────┘ │ │ │
│ │ └────────────────────────────────┘ │ │
│ └──────────────────────────────────────┘ │
│ │ │
│ ↓ │
│ Development Report │
│ │
└─────────────────────────────────────────────────────────────────┘
┌─────────────────────────────────────────────────────────────────┐
│ Skill Collaboration Process │
├─────────────────────────────────────────────────────────────────┤
│ │
│ ┌─────────────┐ │
│ │ PDD Process │ Discovers issues requiring professional support│
│ │ Skills │ │
│ └──────┬──────┘ │
│ │ │
│ ├──────────────────────────────┐ │
│ │ │ │
│ ▼ ▼ │
│ ┌──────────────┐ ┌──────────────┐ │
│ │system-arch │ │software-arch │ │
│ │(System Arch) │ │(Software Arch)│ │
│ └──────┬──────┘ └──────┬───────┘ │
│ │ │ │
│ ├───────────────────────────┼─────────────────────────┤ │
│ │ │ │ │
│ ▼ ▼ │ │
│ ┌──────────────┐ ┌──────────────┐ │ │
│ │software-eng │ │ expert-xxx │ │ │
│ │(Code Impl) │ │(Domain Expert)│ │ │
│ └──────┬──────┘ └──────┬───────┘ │ │
│ │ │ │ │
│ └───────────────────────────┼─────────────────────────┘ │
│ │ │
│ ┌──────────┴──────────┐ │
│ ▼ ▼ │
│ Return to PDD Process Result Feedback │
│ │
└─────────────────────────────────────────────────────────────────┘
┌─────────────────────────────────────────┐
│ PDD AI Collaboration Matrix │
└─────────────────────────────────────────┘
Skill/Role │ Scheduler│ Analyzer │ Designer │Implementer│ Reviewer │ Expert
────────────────┼─────────┼─────────┼─────────┼─────────┼─────────┼────────
pdd-main │ ● │ │ │ │ │
pdd-ba │ │ ● │ │ │ │
pdd-extract │ │ ● │ │ │ │
pdd-generate │ │ │ ● │ │ │
pdd-implement │ │ │ │ ● │ │
pdd-reviewer │ │ │ │ │ ● │
pdd-verify │ │ │ │ │ ● │
────────────────┼─────────┼─────────┼─────────┼─────────┼─────────┼────────
system-arch │ │ │ ● │ │ ○ │
software-arch │ │ │ ● │ ○ │ ○ │
software-eng │ │ │ │ ● │ │
────────────────┼─────────┼─────────┼─────────┼─────────┼─────────┼────────
expert-ruoyi │ │ │ ○ │ ○ │ ○ │ ●
expert-activiti │ │ │ ○ │ ○ │ │ ●
expert-mysql │ │ │ ○ │ ○ │ ○ │ ●
expert-code │ │ │ ○ │ ○ │ ● │ ●
Legend: ● Primary Responsibility ○ Auxiliary Participation │ Space Not Involved
User: I want to develop ZCCZ-2 Asset Transfer module
AI: [Invoking pdd-main skill]
Scanning docs/business-analysis/ directory...
Found module: ZCCZ-2-Asset-Transfer
Path: docs/business-analysis/asset-disposition/ZCCZ-2-Asset-Transfer/
Aggregated design documents:
✓ PRD-Asset-Transfer.md
✓ UseCase-Asset-Transfer.md
✓ BusinessFlow-Asset-Transfer.md
✓ StateDiagram-Asset-Transfer.md
✓ SequenceDiagram-Asset-Transfer-Process.md
Confirm to start business analysis? [Y/n]
User: I want to develop based on these documents
- docs/business-analysis/asset-disposition/ZCCZ-1/PRD-Equity-Transfer.md
- docs/business-analysis/asset-disposition/ZCCZ-1/BusinessFlow-Equity-Transfer.md
- docs/business-analysis/asset-disposition/ZCCZ-1/StateDiagram-Equity-Transfer.md
AI: [Invoking pdd-main skill]
Received 3 design documents:
✓ PRD-Equity-Transfer.md
✓ BusinessFlow-Equity-Transfer.md
✓ StateDiagram-Equity-Transfer.md
Starting business analysis...
User: This module needs to support multi-tenant architecture
AI: [Invoking software-architect skill]
Consultation issue: Multi-tenant architecture design
Passed data:
- Feature requirements: Equity Transfer module
- Existing architecture: Monolithic application
- Constraints: Need to be compatible with existing permission system
[software-architect returns architecture plan]
Architecture Plan:
1. Tenant identifier field design (tenant_id)
2. Data isolation strategy (shared table + tenant field filtering)
3. Tenant context transfer mechanism
4. Key transformation points list
Architecture constraints have been integrated into development specification
User: Encountered permission issue when implementing transfer application list feature
AI: [Invoking expert-ruoyi skill]
Consultation issue: Transfer application list interface permission check failed
Passed data:
- Interface path: /equity/transfer/apply/list
- Error message: Permission check exception
- Related code snippet: [code]
[expert-ruoyi returns solution]
Solution:
1. Check @PreAuthorize annotation configuration
2. Confirm permission identifier in sys_menu table
3. Verify role menu assignment
Solution has been integrated into code implementation
When requirements change:
Requirement Change
↓
pdd-doc-change analyzes change impact
↓
Update related specification documents
↓
Notify affected features
↓
┌─────────────────────────────────────┐
│ If architecture change involved: │
│ → system-architect re-review │
│ If technical solution change: │
│ → Related expert-xxx re-consult │
└─────────────────────────────────────┘
↓
Re-execute code review and verification
This Skill follows PDD framework implementation specification, see pdd-framework-design.md Chapter 9.
| Specification | Core Content |
|---|---|
| Skill Boundary | pdd-code-reviewer (compliance) → expert-code-quality (quality depth), review first then analyze |
| Context Transfer | File system transfer, directory structure specification, supports checkpoint resumption |
| Manual Review | Batch review + detailed review for key features |
| Error Handling | Critical blocks, pause and wait for human after 3 retries |
| PR Management | Manual trigger, Change-grained PR, manual archival |
| Document System | 9 core document types, naming convention, document internal change history |
Code Implementation Complete
│
▼
pdd-code-reviewer (Compliance Review)
│
├── Has Critical issues → Return to fix → Re-review
│
└── No Critical issues
│
▼
expert-code-quality (Quality Depth Analysis)
│
▼
Generate Quality Improvement Tasks (improvement-tasks.md)
│
▼
Enter Next Phase
.pdd-state.jsonArchitecture constraint enforcement skill that monitors code for violations of preset invariants and architectural boundaries. Automatically triggered when users need architecture checks, dependency checks, or module boundary checks. Core responsibility: Ensure architectural coherence and prevent architectural drift. Trigger scenarios: - User requests "check architecture constraints", "check dependency direction", "check module boundaries" - Called by pdd-entropy-reduction coordinator - Automatically triggered after code commits 支持中文触发：架构约束检查、依赖检查、模块边界检查、架构强制、架构漂移、PDD架构约束。
Automated refactoring expert skill that transforms collected quality improvement tasks into concrete code operations. Automatically triggers when users need code refactoring, duplicate elimination, or complexity simplification. Core responsibility: Initiate targeted refactoring PRs regularly in a "small debt repayment" manner to prevent technical debt accumulation. Trigger scenarios: - User requests "refactor code", "eliminate duplicates", "simplify code" - Called by pdd-entropy-reduction coordinator - Refactoring suggestions passed from expert-entropy-auditor 支持中文触发：自动重构、代码重构、消除重复、简化代码、重构专家、PDD重构。
Entropy audit skill that discovers the gap between "design intent" and "code implementation". Automatically triggered when users need technical debt audit, PRD and code consistency check, or AI residue detection. Core responsibility: Identify "AI residue" scattered in the codebase and suggest consolidating them into shared utility packages. Trigger scenarios: - User requests "audit technical debt", "check PRD consistency", "detect AI residue" - pdd-entropy-reduction coordinator calls - Scheduled trigger (recommended weekly) 支持中文触发：熵增审计、技术债务审计、PRD一致性检查、AI残渣检测、PDD熵审计。
PDD Entropy Reduction Agent, continuously monitors and repays technical debt to prevent system decay. Automatically triggered when users need code cleanup, documentation updates, technical debt management, architecture alignment, entropy reduction, or garbage collection. Core Objective: Combat system "entropy increase" and "decay" by periodically running agents to discover documentation inconsistencies or architecture constraint violations. Trigger Scenarios: - User requests "entropy reduction", "clean up technical debt", "code cleanup", "garbage collection" - User requests checking documentation and code consistency - User requests architecture constraint checking - User requests technical debt audit - Scheduled trigger (recommended weekly) - Automatic trigger after code commit (optional) - Automatic trigger after PR merge (optional) 支持中文触发：熵减、清理技术债务、代码清理、文档更新、技术债务管理、架构对齐、垃圾回收、PDD熵减。
Activiti workflow engine expert, proficient in Activiti 7 Core/Cloud architecture, BPMN 2.0 specification, process design and development. Automatically triggered when users involve workflow design, process engine development, BPMN modeling, process deployment management and other issues. Provides BPMN modeling, best practices and solutions. 支持中文触发：工作流设计、流程引擎开发、BPMN建模、流程部署管理、Activiti、工作流、流程设计。
Code quality expert integrating Martin Fowler's refactoring techniques and GoF design patterns to help developers systematically improve code quality. Triggers when users ask about code review, refactoring, design patterns, code smells, SOLID principles, or software architecture improvements. 支持中文触发：代码审查、重构、设计模式、代码异味、SOLID原则、软件架构改进、代码质量。