forge-continuous-enhancement

Iteratively improve the forge container by analyzing build logs and committing approved changes.

5|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/8007342/tillandsias --skill forge-continuous-enhancement-8007342
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: forge-continuous-enhancement
Source: https://github.com/8007342/tillandsias/tree/main/skills/forge-continuous-enhancement
Command: npx skills add https://github.com/8007342/tillandsias --skill forge-continuous-enhancement-8007342

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Improving a containerized development environment requires disciplined, incremental work: reviewing build logs, filing findings, and only implementing changes that have approved plans. This Skill enforces that discipline so agents enhance the forge environment autonomously without pushing unreviewed changes to main. ## Core Features & Use Cases - Build Log Diagnostics: Review Containerfile build output and telemetry logs to identify warnings, errors, and unoptimized layers. - Plan-Gated Implementation: File findings and proposals under plan directories when no approved packet exists, and claim approved packets before editing implementation files. - Safe Autonomous Commits: Commit and push issue reports, proposals, or claimed implementation checkpoints without ever pushing directly to main. - Use Case: Run inside the tillandsias codebase in YOLO mode to have an agent analyze the latest build-install.log, file enhancement proposals, and implement an approved plan packet as a durable checkpoint. ## Quick Start Run tillandsias with opencode and ask the agent to use the forge-continuous-enhancement skill to review the latest build logs and file any improvement proposals.

Frequently Asked Questions about forge-continuous-enhancement

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

FAQPage Schema
How do I run the forge-continuous-enhancement skill?▼

Run it inside the tillandsias codebase, for example with tillandsias --opencode --prompt "Use the /forge-continuous-enhancement skill". The agent then reviews build logs and follows the plan-gated workflow.

How does the skill decide whether to implement changes?▼

It checks for an approved plan packet first. If none exists, it only files findings and proposals under plan/issues/ or plan/forge-improvements/proposals/ without editing implementation files.

Can the agent push changes directly to the main branch?▼

No. The workflow explicitly forbids pushing directly to main. Agents commit and push issue reports, proposals, or claimed implementation checkpoints instead.

What prerequisites are required before using this skill?▼

Opencode, codex, or claude permission files must be loaded in YOLO mode with near-full permissiveness, and telemetry logging must be available in the development environment for build output analysis.

What happens when no approved plan packet exists?▼

The agent does not apply product changes. It files findings, bugs, and enhancement proposals under ./plan/issues/ or plan/forge-improvements/proposals/ and commits those before exiting.