using-hyper
Use when starting any conversation - establishes skill selection and the local task-doc workflow
What this skill does
<skill_overview> Skills are mandatory when they apply, and substantial work must stay grounded in local task docs. </skill_overview> <rigidity_level> HIGH FREEDOM - The meta-process is rigid: check for skills, read them from disk, announce usage, and keep work anchored in `plans/active/`. </rigidity_level> <quick_reference> 1. Check if any skill applies. 2. Read the relevant `SKILL.md` from disk. 3. Announce which skill you are using. 4. For substantial work, create or resume a local `plans/active/<slug>/`. 5. Keep `plan.md`, `context.md`, and `tasks.md` current. </quick_reference> <when_to_use> - At the start of every conversation - Before starting any non-trivial task - Before editing skills, hooks, docs, or code </when_to_use> <the_process> ## 1. Check for skills first - If a skill matches, use it. - Never rely on memory; read the file from disk. - Announce the skill before acting. ## 2. Ground large work in task docs For features, rewrites, and multi-step tasks: - `brainstorming` shapes the work - `writing-plans` distills it into task docs - `executing-plans` implements the current `Now` slice Use: - `plans/active/<slug>/plan.md` - `plans/active/<slug>/context.md` - `plans/active/<slug>/tasks.md` These task directories are local working state. Delete the finished directory instead of archiving it. ## 3. Treat the docs as distinct tools - `plan.md` is the approved intent and acceptance contract - `context.md` is the living discovery log - `tasks.md` is the rolling execution backlog ## 4. Verify before claiming completion Use `verification-before-completion` before any completion claim. </the_process> <examples> <example> <scenario>Developer jumps into implementation with no task directory</scenario> <why_it_fails> - The plan drifts out of memory - Implementation learns things that never get written down - Resumption after compaction becomes guesswork </why_it_fails> <correction> Create or resume a local `plans/active/<slug>/` first, then keep `context.md` and `tasks.md` updated as reality changes. </correction> </example> <example> <scenario>Developer finds a matching skill but works from memory</scenario> <why_it_fails> - Skills evolve - Important steps get skipped - The user cannot tell whether the workflow was actually followed </why_it_fails> <correction> Read the current `SKILL.md`, announce it, then follow it. </correction> </example> </examples> <integration> Common path: - `brainstorming` - `writing-plans` - `executing-plans` - `review-implementation` - `verification-before-completion` </integration>
Related in Productivity
gitea-workflow
IncludedOrchestrate agile development workflows for Gitea repositories using the tea CLI. Use when working with Gitea-hosted repos and asking to 'run the workflow', 'continue working', 'what's next', 'complete the task cycle', 'start my day', 'end the sprint', 'implement the next task', or wanting guided step-by-step development assistance. Keywords: workflow, orchestrate, agile, task cycle, sprint, daily, implement, review, PR, standup, retrospective, gitea, tea.
microsoft-graph-gateway
IncludedRoute Microsoft Graph work in this workspace. Use when users want to read or write Outlook mail, calendar events, contacts, OneDrive or SharePoint files, Teams, Planner, To Do, users, groups, directory data, or arbitrary Microsoft Graph endpoints from VS Code. Prefer WorkIQ for common read scenarios. Use Microsoft Graph for write actions and gap-read scenarios that need exact Graph properties, filters, permissions, or endpoints.
copilotkit
IncludedUse when building with CopilotKit — setup, development, integrations, debugging, upgrading, or contributing. Routes to the appropriate specialized skill based on the task.
wordly-wisdom
IncludedProvides calibrated decision analysis using Charlie Munger-style multiple mental models, inversion, incentive mapping, circle-of-competence checks, misjudgment audits, second-order effects, and forecast updates. Use when the user asks for an oracle take, a hard call, a decision memo, a premortem, an outside view, a red-team, a sanity-check, what am I missing, think this through, or wants a strategy, hire, investment, plan, product, partnership, or major life choice analysed. Avoid for simple factual lookups or time-sensitive legal, medical, or market questions without fresh evidence.
swain-session
IncludedSession management and project status dashboard. Owns the full session lifecycle (start/work/close/resume), focus lane, bookmarks, worktree detection, and tab naming. Also serves as the project status dashboard — shows active epics, progress, actionable next steps, blocked items, tasks, GitHub issues, and recommendations. Worktree creation is deferred to swain-do task dispatch (SPEC-195). Triggers on: 'session', 'status', 'what's next', 'dashboard', 'overview', 'where are we', 'what should I work on', 'show me priorities', 'bookmark', 'focus on', 'session info'.
gandi
IncludedComprehensive Gandi domain registrar integration for domain and DNS management. Register and manage domains, create/update/delete DNS records (A, AAAA, CNAME, MX, TXT, SRV, and more), configure email forwarding and aliases, check SSL certificate status, create DNS snapshots for safe rollback, bulk update zone files, and monitor domain expiration. Supports multi-domain management, zone file import/export, and automated DNS backups. Includes both read-only and destructive operations with safety controls.