Loading...
Loading...
Found 7 Skills
Use to drive consistent forecast methodology, grading, and inspection cadences.
Help users build and scale product operations functions. Use when someone is scaling a product team, struggling with cross-functional coordination, needs to standardize product processes, or wants to improve how insights reach product teams.
Triggers only when the user wants to do spec coding.
Meta-skill enforcing skill discovery and invocation discipline through mandatory workflows. Use when starting any conversation to check for relevant skills before any response, ensuring skill-first workflow before proceeding.
Update documentation based on lessons learned. Use after completing work to capture learnings and prevent future issues.
Used when a Spec Pack is completed, reusable assets need to be promoted to the project SSOT (ADR/contract/ops/NFR/registry), and there are risks of "contaminating the project with full package replication / skipping spec-context / mistaking merge-back for git merge".
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.