managing-as-aramaki

Analyze project requirements and design strategic directives without code edits.

2|2|Updated Feb 9, 2017
One-click install
npx skills add https://github.com/sumik5/dotfiles --skill managing-as-aramaki
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: managing-as-aramaki
Source: https://github.com/sumik5/dotfiles/tree/main/claude-code/skills/managing-as-aramaki
Command: npx skills add https://github.com/sumik5/dotfiles --skill managing-as-aramaki

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill defines the Product Owner role for strategic planning, worktree decisions, and interactions with Manager and Developer Agents.

Core Features & Use Cases

  • Strategy delegation: Create high-level plans and translate to actionable steps.
  • Worktree governance: Decide when to create or reuse worktrees with proper approvals.
  • Interaction protocol: Clear handoffs to Manager and Developer Agents.

Quick Start

Propose a plan for a new feature including worktree naming and expected outcomes.

Frequently Asked Questions about managing-as-aramaki

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

FAQPage Schema
How do I plan a new feature with strategic direction and worktree decisions?

Strategic planning involves analyzing requirements, defining scope, selecting technologies, and deciding whether to create a new worktree or reuse an existing one. This Skill performs that analysis and produces Manager Agent directives with goals, implementation policy, worktree details, constraints, and priorities—without writing code itself.

When should I create a new worktree versus reusing an existing one?

Worktree governance decisions depend on project scope and complexity. This Skill evaluates multi-phase scenarios like new features, architecture evolution, and cross-team initiatives to determine whether a new worktree is required, then delegates execution to the Manager Agent.

How do I structure handoffs between planning, management, and development agents?

This Skill defines the interaction protocol between Product Owner, Manager, and Developer roles. It produces formal directives that specify goals, implementation policy, constraints, and priorities, enabling clear delegation and execution without the strategist performing implementation work.

What's the difference between strategy delegation and implementation?

Strategy delegation focuses on high-level planning, scope definition, technology selection, and worktree decisions—avoiding code edits. This Skill operates as a non-implementation strategist, following formal analysis workflows and producing actionable Manager Agent directives for execution.

Can I use this for complex, multi-phase projects with cross-team collaboration?

Yes. This Skill is designed for complex, multi-phase scenarios including new feature planning, architecture evolution, and cross-team initiatives where requirements need formal analysis, scope definition, and worktree orchestration before implementation begins.