project-agent-skills

Design software system architecture using requirements, constraints, data models, APIs, integrations, dependencies, and technical tradeoff analysis. Use when deciding how a system or feature will fundamentally work.

Break software milestones, features, epics, requirements, and architecture plans into executable stories, tasks, and subtasks with clear boundaries and acceptance criteria.

Analyze software project dependencies, blockers, prerequisite work, critical paths, ownership constraints, external dependencies, and sequencing risks. Use when preventing execution deadlocks or delivery surprises.

Estimate software project effort, complexity, uncertainty, capacity, cost, and delivery ranges using scoped work, decomposed tasks, dependencies, and implementation risk.

Define measurable outcomes, KPIs, success criteria, acceptance thresholds, and decision criteria for software products, features, projects, or initiatives. Use when establishing what success looks like.

Generate and frame software product or feature ideas using user problems, market signals, constraints, and opportunity analysis. Use when brainstorming, discovering opportunities, or deciding what should exist and why it matters.

Prioritize software project work items using impact, urgency, dependencies, risk, and effort analysis. Use when planning milestones, ordering backlog items, or deciding what to work on next.

Plan software product or feature roadmaps using milestones, sequencing, release phases, dependencies, risks, and learning goals. Use when creating a high-level execution path.

Schedule software project work using priorities, estimates, dependencies, capacity, ownership, sprint plans, timelines, and delivery checkpoints. Use when organizing execution order and who does what when.

Define software project scope, MVP boundaries, non-goals, included work, excluded work, and acceptance boundaries. Use when preventing uncontrolled expansion or clarifying what will and will not be built.

Validate software product or feature ideas using user interviews, market evidence, feasibility checks, technical spikes, and prototypes. Use when confirming whether an idea is worth building and technically possible.

Detect file changes in a repository using multiple strategies. Use when you need to identify what files have been modified, added, or deleted for tasks like version bumping, change logging, or selective testing. Also applies when the user asks "what changed", "which files were modified", or describes needing to know the current state of the workspace — even without explicit git references.