Total 50,396 skills, Project Management has 1845 skills
Showing 12 of 1845 skills
Converts unstructured field notes, text messages, voice-to-text transcripts, or informal subcontractor updates into a properly formatted Solar EPC construction daily report. Use this skill whenever a user provides raw field notes, a dump of information from a site superintendent, a forwarded text thread, or any informal description of a day's construction activity and needs it turned into a structured daily log. Trigger for phrases like "format this into a daily report", "turn this into a daily log", "my super sent me this", "here's what happened on site today", "write up today's progress", or when a user pastes a block of unstructured text that describes construction activity. Also trigger when a user asks how to document a weather delay, crew idle time, or a site condition that affected production. Every unrecorded day of construction is an unprotected schedule claim.
Create detailed phase plan (PLAN.md) with verification loop
Associate two tasks (cross-project support)
Spec-driven development: plan → go → review loop with spec lifecycle states and a project-level feature ledger. Use for planning features, implementing from specs, refining specs, tracking what features exist across specs, and resuming work. Trigger on requests mentioning specs, requirements/design/tasks, spec-help, spec-plan, feature ledger, FEATURES.md, spec-ledger, `.kiro`. IMPORTANT: Never edit spec files without first reading this skill.
Use when starting any feature, project, or design work. Guides collaborative design refinement through incremental questioning before any code is written.
Use the `redmine` CLI to interact with Redmine. Activate when the user asks to create, list, update, close, or search issues, log or view time entries, manage versions or memberships, query projects/users/groups, or perform any Redmine project management task. Also activate when the user says "redmine", "issue", "ticket", "time entry", or references Redmine workflows.
Frameworks from Kim & Mauborgne for creating uncontested market space and making competition irrelevant. Use when reframing competitive strategy, escaping commoditization, designing a new category, or applying Strategy Canvas, ERRC, Six Paths, Three Tiers of Noncustomers, Buyer Utility Map, or Strategic Sequence. Includes selection-bias caveats and inline decline notes for iconic cases that later collapsed.
Produces async communication to stakeholders, primarily non-attendees and secondarily some attendees who want a reference. Translates meeting outcomes into what-it-means language for readers, with channel variants (slack, teams, email, notion, exec-memo) and audience variants (engineering, design, leadership, customer-facing, mixed). Surfaces a primary CTA up front, flags technical-to-business translations for user verification, and detects thread continuation from prior updates.
Break a single epic into implementable story files. Reads the epic, its GDD, governing ADRs, and control manifest. Each story embeds its GDD requirement TR-ID, ADR guidance, acceptance criteria, story type, and test evidence path. Run after /create-epics for each epic.
How to handle "why did this work stop / why is this looping?" assignments. Forensics first on the named tree, surface the exact stop-point, frame the fix as a general product rule that respects three invariants (productive work continues, only real blockers stop work, no infinite loops), and deliver a plan — no code changes — gated by board/CTO approval before child issues are created. Use whenever the issue title or body asks for forensics on a stalled, looping, or "went too deep" tree.
Create a new Architecture Decision Record with sequential numbering and AgentDB registration
Break one active project into independent, ready-to-claim tasks when probe next routes create_tasks.