跳到正文
cccskills
免费在 GitHub 公开

ppp-v2

Combined Universal PPP Project Plan Generation Protocol v2.1 - Advanced project-management micro-process engineer that decomposes grand visions into 80+ file, 1000+ action project plans with test-first implementation specifications. Triggers on "PPP", "[PPP=ON]", "project plan", "build me a plan", "create implementation plan", "break down project", "WBS", "micro-plan". Creates complete Plan-of-Attack directories with exegesis, blueprint, implementation specs, task matrix, milestones, decisions, and master execution documents.

中文简介正在准备中。当前显示原文说明。

ProjectZeroDays/FreeAI_AI_Inference_Workstation星标 5(GitHub 5 + cccskills 0)

实测评分 未实测

查看安装方法

包含的文件(1)

  • SKILL.md9.2 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

Combined Universal PPP Project Plan Generation Protocol v2.1

Binding operational protocol for Perfect Project Planner mode. Execute with mechanical precision, zero deviation, absolute completeness.

Core Ideology (5 Pillars)

  1. Effectiveness - Plan must achieve the strategic objective
  2. Meticulousness - No detail undefined
  3. Efficiency - Optimized timeline with parallelization
  4. Sequentiality - Logical, dependency-aware flow
  5. Manageability - Micro-manageable, assignable steps

Critical Operational Rules

  • Open-source, free tools ONLY
  • NO payment systems
  • NO outside collaboration systems
  • NO public release steps (personal/private use ONLY)
  • NO projected timeline - only instructions
  • DO NOT TRUNCATE any part
  • Senior-developer jargon, professional tone
  • LOCAL-ONLY - nothing published outside local system

Workflow: 14 Phases (Execute Sequentially)

Phase 1: Project Parameter Elicitation (MANDATORY FIRST)

Read references/phase1-elicitation.md for full protocol.

Two scenarios:

Scenario A (User has thorough plan):

  • Do NOT interrogate user
  • Self-interrogate across 8 dimensions:
    1. Goal Definition (min 300-word statement)
    2. Scope Boundaries (IN/OUT of scope lists)
    3. Success Metrics (min 5 quantitative, min 3 qualitative)
    4. Resource Inventory (tech, access, assets)
    5. Constraint Identification (with circumvention plans)
    6. Assumption Documentation (with confidence ratings)
    7. Information Gap Analysis (research until 90%+ confidence)
    8. Ambiguity Elimination (resolve all vague language)

Scenario B (User has vague idea):

  • Rigorously interrogate user across 6 categories
  • Iterative deepening until high-level overview confirmed
  • Then transition to Scenario A protocol

Confirmation Gate:

Based on your answers and my analysis, I understand:
- Goal: [summary]
- Scope: [summary]
- Success: [summary]
- Resources: [summary]
- Constraints: [summary]
- Assumptions: [summary]
- Information Gaps: [summary]

I will not truncate the project plan or any part of its files or instructions.

Is this correct? (Respond YES to proceed)

DO NOT PROCEED until explicit YES.

Phase 2: Source Material Analysis (If Applicable)

Read references/phase2-source-analysis.md.

Execute ONLY if project involves integrating, porting, or extending existing systems.

  • Request/identify source materials
  • Create Source Material Catalog
  • Perform comparative analysis
  • Create Source-to-Target Mapping
  • Identify integration points
  • Gap analysis
  • Create architecture map

Phase 3: Plan Directory Structure Creation

Read references/phase3-directory-structure.md.

Create EXACTLY:

project-plan/
├── exegesis/
│   ├── intent-narrative.md
│   ├── objectives.md
│   ├── requirements.md
│   └── instructions/
├── blueprint/
│   ├── architecture.md
│   ├── tech-stack.md
│   ├── interconnections.md
│   └── instructions/
├── implementation/
│   ├── feature-specs/
│   │   ├── [feature-01].md
│   │   └── ...
│   └── instructions/
│       └── feature-specs/
├── task-matrix/
│   ├── wbs-full-tree.md
│   ├── linear-micro-plan.md
│   └── instructions/
├── milestones/
│   ├── success-criteria.md
│   └── instructions/
├── decisions/
│   ├── decision-log.md
│   └── instructions/
├── master-documents/
│   ├── MASTER-EXECUTION-INSTRUCTIONS.md
│   ├── EXECUTION-CHECKLIST.md
│   └── AI-AGENT-START-PROMPT.md
└── completion-log.md

Phase 4: Exegesis Section Creation

Read references/phase4-exegesis.md.

CRITICAL: Exegesis describes WHAT and WHY, never HOW.

Create:

  • intent-narrative.md - Vision (300+ words), Purpose (150+ words), Design Philosophy, End State, Scope, Success Criteria
  • objectives.md - Primary (min 5), Secondary (min 3), Non-Objectives
  • requirements.md - Functional (min 10), Non-Functional (min 5), Integration, Technology

Phase 5: Blueprint Section Creation

Read references/phase5-blueprint.md.

Create:

  • architecture.md - Components, layers, patterns, diagrams
  • tech-stack.md - Technologies with justification
  • interconnections.md - Data flows, API contracts, events

Phase 6: Implementation Section Creation

Read references/phase6-implementation.md.

THIS IS WHERE MOST PLANS FAIL.

Create ONE feature spec per feature (min 20+ for complex projects).

Each feature spec MUST contain:

  • Purpose
  • What to Build (NOT how)
  • Core Components
  • Functionality
  • Integration Points
  • UI (if applicable)
  • Data Model (if applicable)
  • Success Criteria (min 5)
  • Dependencies
  • Test Requirements (min 10)

Phase 7: Task Matrix Creation

Read references/phase7-task-matrix.md.

Create:

  • wbs-full-tree.md - 100+ tasks, hierarchical
  • linear-micro-plan.md - 1000+ atomic actions, dependency order

Phase 8: Instruction Files Creation

Read references/phase8-instructions.md.

CRITICAL STEP - Most plans miss this.

For EVERY plan file, create corresponding .md.instructions file.

Include test-first implementation protocol for ALL implementation files:

  1. READ instruction file
  2. READ plan file
  3. CREATE TESTS FIRST
  4. VERIFY TESTS FAIL
  5. IMPLEMENT step by step
  6. RUN TESTS after each step
  7. FIX IMPLEMENTATION only
  8. VERIFY ALL PASS
  9. Document in completion-log.md
  10. Git commit
  11. Proceed to next file

Phase 9: Milestones Section Creation

Read references/phase9-milestones.md.

Create success-criteria.md with min 20 success criteria.

Format:

## SC-[N]: [Feature/Area Name]
**Criteria**: [What must be true]
**Verification Steps**: [Numbered steps]
**Pass**: [Condition for passing]
**Fail**: [Condition for failing]
**Owner**: [Role responsible]

Phase 10: Decisions Section Creation

Read references/phase10-decisions.md.

Create decision-log.md with min 10 decisions.

Format:

## [ID]: [Decision Name]
**Decision**: [What was decided]
**Rationale**: [Why this choice]
**Alternatives Considered**: [Other options]
**Consequences**: [Trade-offs]
**Date**: [When decided]
**Status**: [Proposed/Accepted/Superseded]

Phase 11: Master Execution Documents Creation

Read references/phase11-master-docs.md.

Create:

  • MASTER-EXECUTION-INSTRUCTIONS.md - Single entry point
  • EXECUTION-CHECKLIST.md - Step-by-step checklist
  • AI-AGENT-START-PROMPT.md - Self-contained agent prompt

Phase 12: AI Agent Start Prompt Creation

Content defined in Phase 11. Ensure AI-AGENT-START-PROMPT.md is complete.

Phase 13: Validation Loop (MANDATORY)

Read references/phase13-validation.md.

Validate ALL:

Completeness:

  • All directories created
  • All files created
  • All instruction files created
  • WBS has 100+ tasks
  • Linear plan has 1000+ actions
  • Min 20 feature specs
  • Min 10 functional requirements
  • Min 5 non-functional requirements
  • Min 5 primary objectives
  • Min 3 secondary objectives
  • Min 20 success criteria
  • Min 10 decisions

Detail:

  • Feature specs describe WHAT not HOW
  • Instruction files describe HOW
  • Implementation instructions include test-first
  • Test files specify 20+ tests
  • WBS leaf tasks completable in hours
  • Linear plan actions are single commands

Consistency:

  • No contradictions
  • Dependencies consistent
  • Technology choices consistent
  • Integration points match
  • Success criteria match objectives

Executability:

  • Agent can start at file 1
  • All commands exact and runnable
  • All paths absolute and correct
  • All test files creatable from specs

IF ANY CHECK FAILS, REVISE UNTIL ALL PASS.

Phase 14: Final Output Generation

Present:

  • Summary (total files, specs, tests, actions)
  • Complete directory tree
  • Execution order
  • Next steps

Quick Reference Files

PhaseReference File
1references/phase1-elicitation.md
2references/phase2-source-analysis.md
3references/phase3-directory-structure.md
4references/phase4-exegesis.md
5references/phase5-blueprint.md
6references/phase6-implementation.md
7references/phase7-task-matrix.md
8references/phase8-instructions.md
9references/phase9-milestones.md
10references/phase10-decisions.md
11references/phase11-master-docs.md
13references/phase13-validation.md

Minimum Quantities (Complex Projects)

ItemMinimum
Feature Specs20+
Functional Requirements10+
Non-Functional Requirements5+
Primary Objectives5+
Secondary Objectives3+
Success Criteria20+
Decisions10+
WBS Tasks100+
Linear Plan Actions1000+
Tests per Feature20+
Total Tests250+
Total Files80+

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

WCAG compliance, accessibility testing, ARIA patterns, screen reader optimization, and keyboard navigation. Use when the user asks about making apps accessible, WCAG guidelines, ARIA attributes, screen reader support, or accessibility audits.

中文简介正在准备中。当前显示原文说明。

ProjectZeroDays/FreeAI_AI_Inference_Workstation52026年9月4日 更新

ace-music

免费

Generate AI music using ACE-Step 1.5 via ACE Music's free API. Use when the user asks to create, generate, or compose music, songs, beats, instrumentals, or audio tracks. Supports lyrics, style prompts, covers, and repainting. Free API, no cost.

中文简介正在准备中。当前显示原文说明。

ProjectZeroDays/FreeAI_AI_Inference_Workstation52026年9月4日 更新

A continuously adaptive skill suite that empowers Clawdbot to act as a versatile coder, business analyst, project manager, web developer, data analyst, and NAS metadata scraper. It intelligently discovers free resources, adapts to user context, and ensures reliable, proven guidance across multiple domains.

中文简介正在准备中。当前显示原文说明。

ProjectZeroDays/FreeAI_AI_Inference_Workstation52026年9月4日 更新

High-fidelity intelligence gathering and data assimilation. Focuses on synthesizing fragmented data into a comprehensive target operational picture.

中文简介正在准备中。当前显示原文说明。

ProjectZeroDays/FreeAI_AI_Inference_Workstation52026年9月4日 更新

Use when Codex needs proactive task queues, heartbeat routines, scheduled follow-up, or continuous work loops instead of waiting for prompts.

中文简介正在准备中。当前显示原文说明。

ProjectZeroDays/FreeAI_AI_Inference_Workstation52026年9月4日 更新

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.

中文简介正在准备中。当前显示原文说明。

ProjectZeroDays/FreeAI_AI_Inference_Workstation52026年9月4日 更新

查看 ProjectZeroDays 的全部技能

报告此技能的问题