Build
A personal Claude Code environment. Persistent memory, loop detection, 15 skills, and lifecycle hooks. macOS, Linux, and Windows.
npx -y skills add puukis/lstack --skill buildAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Plan then implement with an explicit approval gate between phases — invoked via /build
SKILL.md
1.2 KB, 216 tokens by cl100k_base, as published. Nobody here has run it
Build — plan then implement, with approval gate between phases
Activation
Invoked via /build. Use for any task that involves writing new code.
Process
Phase 1 — Planning (runs /planner behavior): Ask 1-3 clarifying questions. Wait for answers. Produce a numbered task list with complexity estimates. Create TodoWrite entries for all tasks. Output: "Plan complete. Reply 'go' to start implementation, or give feedback." STOP. Wait for user response. Do not proceed until 'go' or equivalent is received.
Phase 2 — Implementation (runs /engineer behavior): Work through TodoWrite tasks in order. Mark each in_progress before starting, completed when done. Run tests after each logical unit of work, not just at the end. Report completion with a summary of what was built and test results.
Constraints
- Never skip Phase 1.
- Never start Phase 2 without explicit user approval.
- Never batch multiple unrelated features into one /build run.