Loading...
Loading...
Found 45 Skills
Use to coordinate approvals, communications, and accountability across teams for feedback programs.
Define or update the project governing principles in .specify/memory/constitution.md
Use when evaluating ideas in voting phase. Be aggressive - score misaligned or poor ideas low enough to veto, score weak proposals below approval, score strong aligned ideas high. First check directive, then vote.
Guides actuarial consulting engagements—client scoping and SOW design, stakeholder communication (CFO, risk, boards, regulators at overview level), due diligence and M&A actuarial support, reserving/pricing/capital review programs, model validation and opinion support, regulatory interaction prep, and deliverable governance (memos, exhibits, management presentations). Use when the user mentions actuarial consulting, actuarial engagement, reserve opinion, due diligence actuarial, model validation engagement, actuarial memo, SOW actuarial, regulatory actuarial, M&A reserves, or actuarial review—not deep technical modeling execution (actuary), P&C line education only (property-casualty-insurance), legal advice (commercial-counsel), or generic management consulting without actuarial lens (business-consultant).
CEO/Founder-mode plan review. Rethink the problem, find the 10-star product, challenge premises, expand scope when it creates a better product. Four modes: SCOPE EXPANSION (dream big), SELECTIVE EXPANSION (hold scope + cherry-pick), HOLD SCOPE (maximum rigor), SCOPE REDUCTION (strip to essentials). Adapted from gstack/plan-ceo-review (Garry Tan, MIT license).
Amend an existing plan file — add tasks, modify pending or delegated tasks, and mark completed tasks that are invalidated by the change as [>] (needs re-run). Walks through analysis, cascading impact, and user confirmation before touching the file. When memory (wiki substrate) exists, it may also preserve durable amendment findings there. Reports goal impact and routes intent, boundaries, or validation changes to loam::setting-goals.
Determine if proposed changes require an RFC. Use when planning significant changes, before starting major work, or when asked whether an RFC is needed.
Use when a request or repository needs roadmap decomposition before spec writing because milestone boundaries, module grouping, or independently reviewable tasks are unclear.
Individual project health assessment skill for evaluating project status across multiple dimensions. Provides early warning of troubled projects.