Senior Project Manager

Convert project specifications into development task lists with acceptance criteria.

20|9|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/WebWakaHub/manus-agency-skills --skill senior-project-manager-webwakahub
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Senior Project Manager
Source: https://github.com/WebWakaHub/manus-agency-skills/tree/main/agency-project-management-project-manager-senior
Command: npx skills add https://github.com/WebWakaHub/manus-agency-skills --skill senior-project-manager-webwakahub

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps turn a project specification into clear, realistic development tasks so teams can build from exact requirements instead of vague assumptions.

Core Features & Use Cases

  • Specification analysis: Reads the actual site spec and extracts the requirements that matter without adding unnecessary scope.
  • Task breakdown: Converts features into actionable developer tasks with acceptance criteria that are easy to implement and verify.
  • Technical planning: Identifies the stack, integration needs, and implementation constraints for web projects using Laravel, Livewire, and FluxUI.
  • Use case: A product or project lead can use it to transform a client brief into a structured task list for the engineering team.

Quick Start

Use this skill to review the project specification and generate a realistic development task list with clear acceptance criteria.

Frequently Asked Questions about Senior Project Manager

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

FAQPage Schema
How do I convert project specifications into actionable development tasks for Laravel and Livewire?

Converting project specifications into actionable development tasks requires extracting exact requirements, identifying the Laravel and Livewire stack constraints, and generating task-level acceptance criteria. This Skill analyzes your spec to produce a structured task list without adding unsupported features.

How do I break down a client brief into developer tasks with clear acceptance criteria?

Breaking down a client brief into developer tasks involves reading the actual site spec, extracting the requirements that matter, and converting features into actionable tasks. It generates clear acceptance criteria so teams can build from exact requirements instead of vague assumptions.

What is the best way to perform scope control when planning web development projects?

Scope control in web development planning is achieved by requiring exact requirement quoting from the specification and strictly avoiding the addition of unsupported features. This ensures the generated task list reflects only the requested functionality without unnecessary scope expansion.

Can I use this skill for technical planning and stack identification with FluxUI?

Yes, you can use this skill for technical planning with FluxUI. It identifies the stack, integration needs, and implementation constraints specifically for web projects using Laravel, Livewire, and FluxUI, converting client briefs into structured engineering outputs.

Does this project planning approach work without adding unsupported features to the spec?

Yes, this project planning approach works by enforcing strict scope control without adding unsupported features. It requires exact requirement quoting from the specification to ensure the generated development tasks and implementation notes remain fully aligned with the original client brief.