본문으로 건너뛰기
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(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

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 / 1,000자

이 양식은 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의 스킬 모두 보기

이 스킬의 문제 신고