project-manager

Coordinate software project execution into feature specs, plans, and tasks.

1|Updated Feb 26, 2026

Search Tags:#planning #markdown #orchestration #workflows #project-management #task-delegation

Ready to run

npx skills add https://github.com/aberrantCode/llm_skills --skill project-manager-aberrantcode

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: project-manager
Source: https://github.com/aberrantCode/llm_skills/tree/main/gemini/skills/project-manager
Command: npx skills add https://github.com/aberrantCode/llm_skills --skill project-manager-aberrantcode

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Coordinating the end-to-end lifecycle of software projects from a single prompt is error-prone and requires multiple artifacts. This skill provides a markdown-driven pipeline that derives a feature spec, a plan, and a set of tasks, all stored in a shared, versioned workspace.

Core Features & Use Cases

End-to-end orchestration: drives feature-driven development from initial prompt to delivered code using a centralized markdown workflow.
Plan generation & task delegation: converts feature specs into phased plans and assigns tasks to worker agents with clear roles.
Monitoring, failure recovery, and archival: tracks progress via completion sentinels, creates corrective tasks on failure, and archives finished work for audit.

Quick Start

Provide a single project prompt to initialize the initial feature spec and plan using the Markdown templates.

Frequently Asked Questions about project-manager

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

FAQPage Schema

How do I orchestrate end-to-end project execution from a single prompt?▼

End-to-end project orchestration from a prompt derives feature specs, phased plans, and delegated tasks into versioned markdown artifacts. It drives feature-driven development by converting your initial input into structured deliverables within a shared docs workspace.

What is markdown-driven project management for software workflows?▼

Markdown-driven project management coordinates software workflows using centralized templates for feature specs and tasks. It enforces feature interviews, phased plan generation, and archival governance to maintain structured, versioned documentation throughout the project lifecycle.

How do I convert feature specs into delegated tasks for worker agents?▼

Converting feature specs into delegated tasks involves phased plan generation that assigns clear roles to worker agents. The system tracks progress via completion sentinels and creates corrective tasks automatically upon failure, ensuring continuous workflow execution.

Can I use markdown templates to manage feature-driven development in a shared docs workspace?▼

Markdown templates manage feature-driven development by storing generated specs, plans, and tasks in a shared, versioned workspace. This approach requires no external dependencies and relies entirely on centralized markdown files for project coordination and artifact archival.

What is the best way to monitor task completion and handle failure recovery in project orchestration?▼

Monitoring task completion and handling failure recovery relies on sentinel-based tracking and automated corrective task creation. When delegated tasks fail, the system generates corrective actions and archives finished work for audit, maintaining project continuity without manual intervention.

When do I need sentinel-based completion for workflow orchestration?▼

Sentinel-based completion is needed for workflow orchestration when tracking phased task delegation across worker agents. It provides automated progress verification, triggers failure recovery workflows, and ensures finished project artifacts are properly archived for governance.