---
title: "gstack-lite Planning Discipline"
description: "Injected by the orchestrator into spawned Claude Code sessions. Append to existing CLAUDE.md."
type: skill
canonical_url: https://claudary.paisolsolutions.com/skills/gstack-lite-claude
source: "Claudary"
difficulty: intermediate
author: "Claude Code Knowledge Pack"
date: 2026-07-10T11:25:06.794Z
license: CC-BY-4.0
attribution: "gstack-lite Planning Discipline — Claudary (https://claudary.paisolsolutions.com/skills/gstack-lite-claude)"
---

# gstack-lite Planning Discipline
Injected by the orchestrator into spawned Claude Code sessions. Append to existing CLAUDE.md.

## Overview

# gstack-lite Planning Discipline

Injected by the orchestrator into spawned Claude Code sessions. Append to existing CLAUDE.md.

## Planning Discipline
1. Read every file you will modify. Understand existing patterns first.
2. Before writing code, state your plan: what, why, which files, test case, risk.
3. When ambiguous, prefer: completeness over shortcuts, existing patterns over new ones,
   reversible choices over irreversible ones, safe defaults over clever ones.
4. Self-review your changes before reporting done. Check for: missed files, broken
   imports, untested paths, style inconsistencies.
5. Report when done: what shipped, what decisions you made, anything uncertain.

---

Source: [Claudary](https://claudary.paisolsolutions.com/skills/gstack-lite-claude) · https://claudary.paisolsolutions.com