agency-senior-project-manager

Convert site specifications into developer task lists with acceptance criteria.

Updated Feb 11, 2026
One-click install
npx skills add https://github.com/augustoheiss/LogicDefense --skill agency-senior-project-manager-augustoheiss
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agency-senior-project-manager
Source: https://github.com/augustoheiss/LogicDefense/tree/main/.gemini/skills/agency-senior-project-manager
Command: npx skills add https://github.com/augustoheiss/LogicDefense --skill agency-senior-project-manager-augustoheiss

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes ambiguity from project specifications by converting written site requirements into developer-ready tasks, reducing scope creep and unclear deliverables.

Core Features & Use Cases

  • Specification analysis: Reads the provided spec file and quotes exact requirements while identifying gaps or unclear items.
  • Task decomposition: Breaks features into specific, 30–60 minute developer tasks with clear acceptance criteria and suggested files to create or edit.
  • Technical extraction & memory: Captures technical stack details (CSS frameworks, FluxUI components, Laravel/Livewire needs), remembers previous projects, and saves tasklists to ai/memory-bank/tasks for future reference.
  • Use Case: Ideal for onboarding a new web project or converting client-written specs into a sprint-plan that developers can implement immediately.

Quick Start

Convert the site specification at ai/memory-bank/site-setup.md into a sprint-ready task list and save it to ai/memory-bank/tasks/myproject-tasklist.md.

Frequently Asked Questions about agency-senior-project-manager

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

FAQPage Schema
How do I convert site specifications into actionable developer tasks for Laravel?

To convert site specifications into developer tasks, the system reads spec files, extracts exact requirement quotes, identifies gaps, and breaks features into 30–60 minute task items. It outputs task lists with clear acceptance criteria and suggested files to edit, specifically tailored for Laravel/Livewire projects.

What is the best way to enforce realistic scope constraints from written project requirements?

Enforcing scope constraints from project requirements is done by analyzing spec files to extract exact requirement quotes and identify gaps. This prevents scope creep by decomposing features into specific, actionable developer tasks with strict acceptance criteria.

Does this task planning process work with Livewire and FluxUI component specifications?

Task planning works with Livewire and FluxUI specifications by capturing technical stack details and component requirements during spec analysis. It identifies necessary files to create or edit and generates acceptance criteria tailored to these specific web frameworks.

How do I save generated task lists to a memory bank for future reference?

Saving generated task lists to a memory bank is achieved by writing output task items and acceptance criteria to the ai/memory-bank/tasks path. This stores sprint-ready developer tasks alongside previous project memories for future reference.

Can I use this spec analysis tool for non-Laravel web projects?

You can use this spec analysis tool for non-Laravel web projects because it applies to general web specifications that include stack details and UI component requirements. It extracts requirements and outputs actionable developer tasks regardless of the specific framework.

Why do I need acceptance criteria in generated developer task lists?

Acceptance criteria in developer task lists are needed to remove ambiguity from project specifications and reduce unclear deliverables. They ensure each 30–60 minute task has clear completion requirements, preventing scope creep and guiding implementation.