stack-engineer

Classify unfinished system work for recovery, reimplementation, promotion, parking, or archiving.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Ic1558/0luka --skill stack-engineer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stack-engineer
Source: https://github.com/Ic1558/0luka/tree/main/skills/stack-engineer
Command: npx skills add https://github.com/Ic1558/0luka --skill stack-engineer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The skill addresses the problem of locating, classifying, and choosing between recover, re-implement, promote, park, or archive for unfinished or ambiguous system work within the 0luka stack.

Core Features & Use Cases

  • Continuation Engineering: Navigate system lanes, prototypes, or partial implementations that require continuation without causing architectural drift.
  • Decisions Based on Repo & Runtime Truth: Uses repository and runtime truth for making bounded and correct continuation decisions.
  • Use Case: A partial system feature that lacks clear continuation guidance can be analyzed and classified for recovery, re-implementing, promotion, parking, or archiving.

Quick Start

Initiate a continuation analysis on a system lane 'example_lane' by executing the command 'stack-engineer example_lane'.

Frequently Asked Questions about stack-engineer

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

FAQPage Schema
What is bounded continuation engineering for unfinished software architecture work?

Bounded continuation engineering is the process of locating and classifying unfinished system work to prevent architectural drift. It identifies work states and supports decisions on recovery, reimplementation, promotion, parking, or archiving within a software stack.

How do I decide whether to recover, re-implement, or archive a partial system feature?

To decide whether to recover, re-implement, or archive a partial system feature, you analyze repository and runtime truth. This classifies the work state and supports bounded, correct continuation decisions based on actual system boundaries.

Do I need governance documents and a skill registry to classify system work states?

Yes, classifying system work states requires governance documents and specific skill registry access. These prerequisites ensure bounded continuation decisions align with established architectural boundaries and stack governance.

How do I start a continuation analysis on a system lane?

To start a continuation analysis on a system lane, execute the command 'stack-engineer example_lane'. This initiates the classification process for navigating partial implementations without causing architectural drift.

What is the best way to navigate partial implementations without causing architectural drift?

The best way to navigate partial implementations without causing architectural drift is to use continuation engineering based on repo and runtime truth. This approach identifies work states and manages system boundaries for bounded decisions.