engineering-assistant

Coordinate architecture-first planning and multi-skill orchestration for engineering tasks.

3|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/ldilov/harness-forge --skill engineering-assistant
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: engineering-assistant
Source: https://github.com/ldilov/harness-forge/tree/main/skills/engineering-assistant
Command: npx skills add https://github.com/ldilov/harness-forge --skill engineering-assistant

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

architecture and implementation orchestrator for cross-cutting engineering work. use when a task needs system design, code architecture, refactoring strategy, implementation planning, specialist-skill routing, or explicit project-memory and change-discipline guidance in one surface.

Core Features & Use Cases

  • Architecture-first planning across tasks and repo boundaries
  • Coordination of multiple specialist skills and knowledge packs under a single delivery plan
  • Built-in project-memory and change-discipline guidance to ensure traceability and governance
  • Deliverable-oriented workflow with options, trade-offs, and concrete plan

Quick Start

Trigger the engineering-assistant skill to capture context, constraints, and a unified architecture-driven plan for the task.

Frequently Asked Questions about engineering-assistant

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

FAQPage Schema
How do I plan system design and code architecture for cross-cutting engineering tasks?

Architecture-first planning coordinates system design and code structure decisions across tasks and repo boundaries. It captures context and constraints to produce a unified, architecture-driven delivery plan with clear options and trade-offs.

What is the best way to coordinate multiple specialist skills under a single delivery plan?

Multi-skill orchestration coordinates specialist skills and knowledge packs under a single delivery plan. It routes tasks to appropriate skills while maintaining cohesive coordination and applying safety checks throughout the workflow.

How does project-memory governance ensure traceable decisions during refactoring?

Project-memory governance maintains traceable decisions and change-discipline guidance during refactoring strategies. It records architectural choices and constraints to ensure coordination remains cohesive and auditable across engineering tasks.

When do I need explicit change-discipline guidance for engineering coordination?

Explicit change-discipline guidance is needed when tasks require system design, refactoring strategies, or implementation planning that spans repo boundaries. It ensures traceable decisions and cohesive coordination with safety checks.

Does this approach work for implementation planning across multiple repository boundaries?

Yes, architecture-first planning works across repository boundaries by capturing context and constraints into a unified plan. It coordinates specialist-skill routing and project-memory governance to ensure cohesive delivery.