role-architect

Design large initiatives into design docs, GitHub issues, and PM handoffs.

Updated Feb 22, 2026
One-click install
npx skills add https://github.com/JuroOravec/agents --skill role-architect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: role-architect
Source: https://github.com/JuroOravec/agents/tree/main/.cursor/skills/role/architect
Command: npx skills add https://github.com/JuroOravec/agents --skill role-architect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Designing and executing complex initiatives often stalls at the planning stage. This skill helps convert ambiguous goals into concrete design docs, a prioritized backlog of GitHub issues, and a clear handoff to PMs for prioritization and deployment.

Core Features & Use Cases

  • Create high-level design documents for large goals.
  • Generate GitHub issues and a prioritized task backlog for cross-functional teams.
  • Coordinate with PMs to align prioritization and parallelization across phases and teams.

Quick Start

Break a large goal into a design doc and actionable backlog of GitHub issues.

Frequently Asked Questions about role-architect

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

FAQPage Schema
How do I break down large project goals into actionable GitHub issues?

Designing complex initiatives starts by converting ambiguous goals into a high-level design document. This design doc outlines the multi-phase initiative and provides the structure needed to generate a prioritized backlog of GitHub issues.

What's the best way to create a design doc for multi-phase project planning?

The best way to create a design doc for multi-phase project planning is to use a structured workflow that breaks large goals into a design document, a prioritized backlog of GitHub issues, and coordination hooks for PM handoff.

How do I coordinate PM handoff for prioritization and parallel work across teams?

You coordinate PM handoff by generating a prioritized backlog of GitHub issues alongside a design doc. This provides product managers with the coordination hooks needed to align parallel work across cross-functional teams.

Can I generate a prioritized task backlog for cross-functional teams from a single goal?

Yes, you can generate a prioritized task backlog for cross-functional teams from a single large goal by applying a structured workflow that produces design documents, GitHub issues, and PM coordination hooks.

Do I need a specific project management tool to break big goals into design and tasks?

No specific project management tool is required to break big goals into design and tasks, but the workflow is structured to output GitHub issues and PM coordination hooks to enable prioritization and parallel work.