원클릭으로 Manus에서 모든 스킬 실행

project-plan-review

스타0

포크0

업데이트2026년 4월 10일 00:14

Review checklist for project plans before execution. Includes structural validation, container/VM requirements, cross-reference checks, and performance considerations.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

krmorehead

krmorehead/vm_builds

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Project Plan Review

Use when editing or reviewing project plans in docs/projects/ to ensure completeness, correctness, and prevent common planning mistakes.

Rules

ALWAYS verify dynamic group persistence for separate ansible-playbook invocations
ALWAYS document auth transitions with ordering, re-registration, detection
NEVER split provisioning and site.yml integration into separate milestones
NEVER use proxmox_lxc_default_template - create service-specific template vars
NEVER add "graceful skip" for expected hardware - hard-fail instead
ALWAYS verify container IP offset doesn't collide with existing allocations
NEVER use bare relative paths - they break with molecule scenarios
ALWAYS include rollback plays in playbooks/cleanup.yml for all features

Patterns

Structural validation:

# Dynamic group reconstruction pattern
- name: Reconstruct dynamic group for rollback
  include_tasks: tasks/reconstruct_service_group.yml
  
# Auth transition specification
# Play ordering: SSH key → API token → configure with new auth method
# Detection: verify new auth method before removing old
# Rollback: reverse order of transition

Cross-reference verification:

# Check these exist before completing plan:
- grep for VMID in group_vars/all.yml
- grep for flavor group in inventory/hosts.yml  
- grep for platform in molecule/*/molecule.yml
- grep for cleanup in both cleanup playbooks
- grep for verify assertions in molecule/default/verify.yml

Container IP allocation check:

# Verify offset doesn't collide with existing allocations:
# Current: WG=3, Pi-hole=10, rsyslog=12, HA=14, Jellyfin=15,
# Kodi=16, Moonlight=17, Gaming=18, Kiosk=19, Netdata=21
# WAN hosts use NAT bridge (10.99.x.x) — offsets just need to
# be unique per host. No host IP collision risk.

Anti-patterns

NEVER explain what project plans are in review rules NEVER keep blocked milestones as stubs in current project NEVER omit LXC features declaration (nesting=1, privileged, etc.) NEVER skip image build milestone - configure roles can't install packages

이 저장소의 다른 Skills

같은 저장소

project-structure-rules

krmorehead/vm_builds

Project architecture and design principles for vm_builds Ansible project. Includes bake vs configure patterns, two-role service model, and deployment lifecycle.

2026-04-290

python-code-style

krmorehead/vm_builds

Python code conventions. Functions return errors, .env parsing strips quotes, type hints required.

2026-04-290

early-validation-patterns

krmorehead/vm_builds

Proactive validation patterns to catch issues early, prevent debugging blind, and establish testing habits before problems escalate.

2026-04-280

learn-from-mistakes

krmorehead/vm_builds

Update skills and rules when encountering new issues to prevent recurrence. Includes hard-fail patterns, code custodianship, and mandatory testing requirements.

2026-04-280

lxc-container-patterns

krmorehead/vm_builds

LXC container provisioning and configuration patterns. Use when creating LXC services, managing container networking, or handling LXC template operations.

2026-04-280

molecule-performance

krmorehead/vm_builds

Molecule test performance optimization patterns. Template caching, NTP sync, pct_remote overhead, apt cache, selective rebuilds.

2026-04-280

Project Plan Review

Use when editing or reviewing project plans in docs/projects/ to ensure completeness, correctness, and prevent common planning mistakes.

Rules

ALWAYS verify dynamic group persistence for separate ansible-playbook invocations

ALWAYS document auth transitions with ordering, re-registration, detection

NEVER split provisioning and site.yml integration into separate milestones

NEVER use proxmox_lxc_default_template - create service-specific template vars

NEVER add "graceful skip" for expected hardware - hard-fail instead

ALWAYS verify container IP offset doesn't collide with existing allocations

NEVER use bare relative paths - they break with molecule scenarios

ALWAYS include rollback plays in playbooks/cleanup.yml for all features

Patterns

Structural validation:

# Dynamic group reconstruction pattern - name: Reconstruct dynamic group for rollback include_tasks: tasks/reconstruct_service_group.yml # Auth transition specification # Play ordering: SSH key → API token → configure with new auth method # Detection: verify new auth method before removing old # Rollback: reverse order of transition

Cross-reference verification:

# Check these exist before completing plan: - grep for VMID in group_vars/all.yml - grep for flavor group in inventory/hosts.yml - grep for platform in molecule/*/molecule.yml - grep for cleanup in both cleanup playbooks - grep for verify assertions in molecule/default/verify.yml

Container IP allocation check:

# Verify offset doesn't collide with existing allocations: # Current: WG=3, Pi-hole=10, rsyslog=12, HA=14, Jellyfin=15, # Kodi=16, Moonlight=17, Gaming=18, Kiosk=19, Netdata=21 # WAN hosts use NAT bridge (10.99.x.x) — offsets just need to # be unique per host. No host IP collision risk.

Anti-patterns

name	project-plan-review
description	Review checklist for project plans before execution. Includes structural validation, container/VM requirements, cross-reference checks, and performance considerations.