morpheus

Provide architectural oversight and refactoring guidance across engineering teams.

1|Updated Jan 10, 2026
One-click install
npx skills add https://github.com/drusifer/via --skill morpheus-drusifer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: morpheus
Source: https://github.com/drusifer/via/tree/main/agents/morpheus.docs
Command: npx skills add https://github.com/drusifer/via --skill morpheus-drusifer

SYSTEM DOCUMENTATION & REQUIREMENTS

Solves the problem of unclear architectural direction by providing strategic oversight and refactoring discipline across engineering teams.

Core Features & Use Cases

  • Strategic architecture alignment across squads
  • Refactoring guidance and task decomposition planning
  • Governance and decision-recording for architecture changes

Quick Start

Provide high-level architectural guidance to accelerate design decisions and refactor planning across teams.

Frequently Asked Questions about morpheus

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

FAQPage Schema
What is architectural governance and why is it needed for cross-team engineering?

Architectural governance provides strategic oversight and refactoring discipline across engineering teams, ensuring cross-team alignment and code quality guardrails during design reviews and sprint planning.

How do I plan refactoring tasks and decompose work for engineering squads?

Refactoring guidance and task decomposition planning break down complex architectural changes into executable tasks, delivering artifacts like decision records and task decompositions that engineers use to drive consistent implementation.

Can I use this for sprint planning and architectural design reviews?

Yes, sprint planning and design reviews are core applications where architectural alignment and governance checklists ensure cross-team consistency and maintain code quality guardrails throughout the engineering process.

What's the best way to record architectural decisions for team alignment?

Recording architectural decisions through decision records captures strategic oversight and governance activities, providing executable guidance and artifacts that engineers use to drive consistent design and implementation across squads.

Does this approach to architectural guidance work for multiple engineering squads?

Yes, strategic architecture alignment is designed specifically for cross-team coordination, applying refactoring discipline and governance checklists across multiple squads to maintain consistent code quality and design standards.