apply-shape-changes

Assemble an atomic close bundle with locked-shape document, edits, epic, and one issue.

3|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/kapilvirenahuja/garura --skill apply-shape-changes
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: apply-shape-changes
Source: https://github.com/kapilvirenahuja/garura/tree/main/core/components/skills/apply-shape-changes
Command: npx skills add https://github.com/kapilvirenahuja/garura --skill apply-shape-changes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It converts a session’s accumulated intent and resolutions into a single, approval-gated bundle of deterministic target-shape edits plus the required epic and exactly one engineering follow-up issue.

Core Features & Use Cases

  • Creates the locked shape document: Writes the canonical locked-shape.md from session state so the outcome is human-auditable and structurally consistent.
  • Builds an all-or-nothing edit bundle: Drafts file edits for every impacted target-shape artefact and presents a unified diff preview for one-time approval.
  • Ensures play invariants for deterministic delivery: Enforces guardrails like atomicity (no partial writes), no code-file writes, touchpoint inventory consistency, and canonical epic status handling.
  • Files one code follow-up issue: Creates or updates the now→then epic and files exactly one follow-up issue describing engineering work implied by the shape change.

Quick Start

Use the skill in dry_run mode to assemble and preview the close-bundle for your grill-me session, then re-run with approval_mode interactive to apply the transaction after approval.

Frequently Asked Questions about apply-shape-changes

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

FAQPage Schema
How do I atomically apply shape changes and file engineering follow-up issues after a requirements resolution session?▼

Atomic edit bundles prevent partial writes by validating touchpoint drift and enforcing no code-file edits, guaranteeing deterministic development outcomes and canonical epic status handling during the close transaction.

What is an atomic close bundle for epic management and deterministic development?▼

Atomic edit bundles prevent partial writes by validating touchpoint drift and enforcing no code-file edits, guaranteeing deterministic development outcomes and canonical epic status handling during the close transaction.

How do I preview file edits before applying an atomic write to impacted target-shape artefacts?▼

You preview file edits by running the process in dry_run mode to assemble and view a unified diff of the close-bundle, then re-running in interactive approval mode to apply the transaction after review.

Can I use this approach to enforce guardrails like documentation gating and touchpoint inventory consistency?▼

Yes, you can enforce guardrails by validating against touchpoint drift and forbidden code-path edits, which guarantees documentation gating, touchpoint inventory consistency, and canonical epic status during the atomic write.

Does this deterministic development approach support creating multiple engineering follow-up issues per session?▼

No, deterministic development through this method guarantees exactly one engineering follow-up issue filing behavior per close transaction, alongside creating or updating the now→then epic and writing the locked-shape document.