project-manager

Propose up to three next-step skills from current .documents state and guardrails.

Updated Jan 26, 2026
One-click install
npx skills add https://github.com/hoonzinope/skills --skill project-manager-hoonzinope
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-manager
Source: https://github.com/hoonzinope/skills/tree/main/project-manager
Command: npx skills add https://github.com/hoonzinope/skills --skill project-manager-hoonzinope

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Teams often over-commit by planning multiple skills for every round. This Skill helps identify and propose the minimal set of next-step skills to run, based on current .documents state and enabled skills, to keep workflows lean and efficient.

Core Features & Use Cases

  • Recommends up to 3 skills aligned to the current state and guardrails.
  • Ensures outputs consistently reference docs/IDs and stay under the .documents/ scope.
  • Use Case: After a round of work, generate a concise Runbook with the next steps to take, avoiding unnecessary planning overhead.

Quick Start

Run this Skill to generate a PM Round with up to three recommended skills.

Frequently Asked Questions about project-manager

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

FAQPage Schema
How do I determine the minimal next steps for my workflow automation?

To determine minimal next steps for workflow automation, this skill analyzes your current .documents state and enabled skills, then proposes up to three targeted skills in the smallest effective scope to keep planning lean.

How do I generate a runbook with recommended next steps after a work round?

You generate a runbook with recommended next steps by running this skill to create a concise PM Round, proposing up to three aligned skills that address current workflow triggers and guardrails without unnecessary planning overhead.

What is the best way to avoid over-committing when planning multiple skills?

The best way to avoid over-committing when planning multiple skills is to use this skill to identify the minimal effective set of next-step actions, ensuring outputs reference docs/IDs and stay strictly under the .documents/ scope.

Can I use this workflow planning tool without predefined guardrails?

This workflow planning tool relies on predefined guardrails to function correctly, as it uses them alongside your current .documents state to filter and propose only the most relevant next-step skills for your automation needs.

Do I need existing documentation under .documents/ to use this skill?

Yes, you need existing documentation under .documents/ to use this skill, because it evaluates the current state of those documents and your enabled skills to propose the minimal set of next-step actions with proper docs/IDs references.