skills.rest
claushaas
claushaasCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

phase-implementation-runbook

Enforce the Palette Kit v0.4 runbook for 16-phase development workflows.

Updated Aug 23, 2026
Search Tags:#branching#patch#lint#typecheck#phase-workflow#palette-kit#v0.4
One-click install
npx skills add https://github.com/claushaas/claus-haas-ai-stuff --skill phase-implementation-runbook
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: phase-implementation-runbook
Source: https://github.com/claushaas/claus-haas-ai-stuff/tree/main/skills/phase-implementation-runbook
Command: npx skills add https://github.com/claushaas/claus-haas-ai-stuff --skill phase-implementation-runbook

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enforces the Palette Kit v0.4 small-phase implementation runbook to keep projects aligned with the playbook and guardrails.

Core Features & Use Cases

  • Enforced workflow discipline: Ensures teams follow the 16 phases in order with defined guardrails.
  • Structured branching & validation: Guides branch naming, preflight checks, lint, typecheck, tests, and build steps.
  • Audit-ready patches: Documents and exports a patch summary for reviewers.

Quick Start

Create a new phase branch named phase-<number>-<short-slug> from v0.3, implement scoped changes, run the validation sequence, and generate a patch for review.

Frequently Asked Questions about phase-implementation-runbook

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce a phased development workflow with structured branching and validation?▼

To enforce a phased development workflow, this runbook guides branch creation, scoped implementation, and validation sequences including lint, typecheck, tests, and build across 16 defined phases to maintain project alignment.

What is the correct branch naming convention for phase-driven development?▼

The correct branch naming convention for phase-driven development requires creating branches named phase-<number>-<short-slug> from the v0.3 baseline to ensure structured tracking across the 16 phases.

How do I document code changes for audit-ready patches in a phase workflow?▼

To document code changes for audit-ready patches, you run the required validation sequence and generate a patch summary that exports the scoped implementation details for reviewer inspection.

What validation steps are required before completing a phase implementation?▼

The validation steps required before completing a phase implementation are running lint, typecheck, tests, and build checks in a defined sequence to ensure the scoped changes meet project guardrails.

Does this phase implementation runbook work for projects outside of Palette Kit v0.4?▼

This phase implementation runbook is specifically designed to enforce the Palette Kit v0.4 guardrails and does not apply to projects outside of that framework version.

Related Skills

Explore More Software Engineering Skills→
cshyangcshyang

gsd:workflow:new-project

Initialize repositories, capture requirements, research domains, and create roadmaps for GSD projects.

Community
Advanced
blakesimsblakesims

review-merge

Validate feature branch merge readiness with integration checks and summaries.

Community
Advanced
ViewableGravyViewableGravy

nx-verify

Run typecheck, lint, and test targets sequentially for Nx projects.

Community
Intermediate
letsur-devletsur-dev

git-commit-helper

Generate Spec-Kit-compliant git commit messages with Work Package references.

Official
Intermediate