engineering-workflow

Applies core engineering rules for implementing, reviewing, and delegating work in Lacquer-managed projects.

3|Updated Jun 15, 2026
One-click install
npx skills add https://github.com/patrickserrano/lacquer --skill engineering-workflow-patrickserrano
Or copy as Structured Prompt for Agentβ–Ό
Please help me install this Agent Skill.
Skill: engineering-workflow
Source: https://github.com/patrickserrano/lacquer/tree/main/core/skills/engineering-workflow
Command: npx skills add https://github.com/patrickserrano/lacquer --skill engineering-workflow-patrickserrano

SYSTEM DOCUMENTATION & REQUIREMENTS

πŸ’‘ This Skill includes references (resource) components.

What problem does it solve? Engineering sessions in Lacquer-managed projects need consistent conventions β€” atomic commits, worktree usage, PR-only merges, no lint suppression, and disciplined delegation β€” but these rules are easy to forget or apply inconsistently across tasks. This Skill loads the shared project rules so feature implementation, code review, delegation, and session resumption all follow the same standards. ## Core Features & Use Cases - Fundamental Rules Enforcement: Requires proven-working code, passing tests, atomic commits, git worktrees under .worktrees/, and forbids force flags, lint suppressions, and direct pushes to main. - Agent Delegation Guidance: Distinguishes skills from subagents to avoid Agent type not found errors, and matches delegation patterns (subagent-driven development, evaluator-optimizer, manager-loop, agent teams) to task scope. - Context Management: Prevents mid-task compaction failures through one-task-per-session discipline, deliberate handoffs, subagent exploration offloading, and proactive /compact usage. - Use Case: When starting a feature in any synced project, invoke this Skill to load the applicable rules β€” for example, before delegating Swift work it reminds you that swift-testing-expert is a skill while ios-swift-engineer is the Task subagent. ## Quick Start Use the engineering-workflow skill to implement this feature following the project rules, working in a git worktree with atomic commits and a pull request.

Frequently Asked Questions about engineering-workflow

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

FAQPage Schema
When should I run an adversarial code review before merging?β–Ό

Run a separate adversarial review of the diff for high-risk changes touching security or trust boundaries, concurrency and data-race safety, authentication or authorization, and data-integrity boundaries. Routine changes do not need this extra review step.