Productivity

allgpt-co Skill

Workflow for verifying completed work

allgpt-co Skill

Workflow for executing a project plan

allgpt-co Skill

Workflow for verifying phase completion

allgpt-co Skill

Workflow for discussing phase details

allgpt-co Skill

Workflow for resuming a paused project

allgpt-co Skill

Workflow for diagnosing project issues

allgpt-co Skill

Workflow for completing a milestone

allgpt-co Skill

Workflow for listing phase assumptions

benjaminshoemaker Bundle

Add a properly formatted TODO item to TODOS.md. Use when you need to capture a new task, bug, or feature request during development.

benjaminshoemaker Skill

Implement [ready]-tagged TODO items with commits. Use after /list-todos has clarified requirements and marked items as ready.

benjaminshoemaker Bundle

Attempt automated verification of criteria before falling back to manual. Parses criterion text for automation hints and executes appropriate tool (curl, browser, file check). Invoked by verify-task and phase-checkpoint for MANUAL and MANUAL:DEFER criteria.

benjaminshoemaker Skill

Run code-verification on a specific task. Use to verify a single task's acceptance criteria after implementation.

kangwang42 Bundle

从当前会话、用户纠正、已查看产物和可定位的项目证据中复盘未遵循工作流的问题，分析最早失效环节，并在当前工作目录生成或更新 `workflow.txt` 交接报告。用于用户要求总结本次工作发现的规范缺口、解释为什么没有遵循、把问题带回 EpiAgentKit 后续改进时；也用于在生成报告前整理多个零散纠正。只记录有来源和置信度的事实、推断及候选调整，不替代当前任务的内容 skill，不直接修改 EpiAgentKit 或正式研究产物；在 EpiAgentKit 中依据报告改规则时改用 `epiagentkit-maintenance`，并以完整仓库核验为准。

kastalien-research Skill

DEPRECATED — use workflow Stage 2 (spec + frontmatter claims). Historical HDD docs are in docs/decisions/archive/.

kastalien-research Skill

Orchestrate the full development lifecycle from ideation through merge. Sequences 8 stages with gates, dispatches to stage skills, and maintains workflow state.

kastalien-research Skill

Implement a specification using a TDD-oriented workflow. Extracts requirements, generates tests first, then implements to pass the tests. Includes spiral detection and acceptance gates.

kastalien-research Skill

Execute the implementation plan by dispatching sub-agents for each task. Stage 4 of the development workflow.

kastalien-research Skill

Verify implementation claims by dispatching review agents. Stage 5 of the development workflow.

kastalien-research Skill

Evaluate whether an idea is worth implementing by asking structured questions about outcomes, alignment, and opportunity cost. Stage 1 of the development workflow.

kastalien-research Skill

Iterate on implementation fixes surfaced by review until all claims are verified. Stage 6 of the development workflow.

kastalien-research Skill

Friction-gated refactoring using the Theseus protocol. Prevents scope creep and refactoring fugue state by enforcing file scope boundaries, visa-based expansion, checkpoint audits, and a brittleness counter. Use when refactoring code, restructuring modules, renaming across files, or any task where "structure changes but behavior must stay the same". Triggers on "refactor", "restructure", "rename across", "extract module", "move code", or when a change touches 3+ files without adding features.

kastalien-research Skill

Finalize the workflow by reflecting on the process, moving ADRs, closing issues, and preparing for merge. Stage 8 of the development workflow.

kastalien-research Skill

Execute an implementation by dispatching multiple sub-agents to parallel Git worktrees. Each builds the entire feature independently, and the best implementation is selected and merged.

kastalien-research Skill

This skill should be used before implementing features, building components, or making changes. It guides exploring user intent, approaches, and design decisions before planning. Triggers on "let's brainstorm", "help me think through", "what should we build", "explore approaches", ambiguous feature requests, or when the user's request has multiple valid interpretations that need clarification.

seasonedcc Skill

Organize business logic in app/business/ by domain cohesion and framework independence. Use when creating files in app/business/, adding functions to business files, naming business modules, deciding where to place business logic, or choosing what to import in business code.

seasonedcc Skill

Codify lessons from a completed task on two channels at once — a draft pull request on the project's own content or tooling, plus a detailed anonymized issue on the seasoned-skills package — with every PR marked ready only by the user. Use when a task has met every other Definition of Done criterion, when a /goal goal is met but not yet marked complete, or when the user asks to derive lessons from recent work.

viewway Bundle

Validates outputs, gates, and workflow compliance

bkywksj Skill

任务跟踪与进度管理技能，管理开发任务的创建、分解、状态更新和归档。 触发场景： - 用户需要创建或查看开发任务 - 用户需要更新任务进度或状态 - 用户需要归档已完成的任务 触发词：任务、进度、待办、TODO、跟踪

borkweb Skill

Scopes a coding task before implementation — names the handful of files actually relevant (read/edit these), the areas to leave alone, and any open scope questions, so work doesn't start by reading the whole repo. Fires proactively at the start of substantive, multi-file, or unfamiliar-area work; stays silent on single-file edits, one-line fixes, questions, and continued work in an area already scoped this session. Use when beginning a feature, bug fix, or refactor that could plausibly touch several files or an area not yet seen this session.

garyld1962 Skill

Test file generator — converts TestSpecification objects into valid Vitest .test.ts files with it.todo() stubs.

garyld1962 Skill

Requirements analyst — decomposes task description into testable requirements. Maps Zod schema fields to assertions. Verifies CRUD completeness and return type coverage.

garyld1962 Bundle

Optimize a draft task graph's dependencies and file ownership for safe optional concurrency. Use before execution when scheduling needs work; do not change requirements or create a second lane/wave plan.

garyld1962 Skill

Requirements analyst — decomposes task description into testable requirements. Maps Zod schema fields to assertions. Verifies CRUD completeness and return type coverage.

harshanandak Bundle

Toggle Forge's workflow gates and rails — strong-but-toggleable enforcement. `forge gate enable|disable <gate-id>` flips `workflow.gates.<id>.enabled` in `.forge/config.yaml`; the installed git hooks read resolved config at run time, so disabling a rail makes them genuinely inert. `forge gate approve|reject <issue> <gate>` records durable human-gate approval events; `forge gate status`/`check` query them; `forge control <id> <mandatory|optional|permission>` sets tri-state DECLARED intent (writes the same `enabled` field — no independent runtime enforcement). Use when the user says "disable the gate", "turn off TDD enforcement", "the tdd intent rail is blocking me", "toggle or enable a gate", "loosen enforcement", or "approve a human gate". Common default-ON toggleable rails: `rail.tdd_intent`, `rail.kernel_tracking`, `rail.auto_shepherd` — e.g. `forge gate disable rail.tdd_intent`. NOT for addressing PR review feedback (review), NOT the status snapshot of work in flight (status).

harshanandak Bundle

The flagship Forge orchestrator: given a goal or a ready issue, it composes the stage skills (triage-ready · claim-safety · plan · dev · validate · ship · review · verify) into the right path for the work, running autonomously between human gates and pausing at them. Use this whenever the user wants to work the next ready issue, drive a feature or fix end-to-end, "take this through to a PR", orchestrate the whole workflow with human checkpoints, or asks some form of "what should I work on and get it done" — even if they never say "smith" or "orchestrate". Reach for it especially when the request spans multiple stages (plan → build → ship) or asks to keep a human in the loop at intent, plan, or merge. Prefer a single stage skill only when the user explicitly wants just that one step (e.g. "just open the PR").

harshanandak Bundle

Forge kernel — umbrella index/router for a Forge project. Reach for this FIRST when orienting rather than executing: at session start, when you need the map of how the system fits together, or when unsure WHICH skill or `forge` verb a task belongs to. It indexes `smith` (end-to-end orchestrator), the stage ladder (plan → dev → validate → ship → review → verify), the utility/issue skills, and the day-to-day `forge` CLI verbs. Trigger on "how does the Forge workflow work", "which forge command or skill for X", "I'm new here, how is Forge set up", or "should this be a Forge issue or a TodoWrite". Index layer only — hand off the doing: rank/pick the next ready issue → `triage-ready`; current stage / "where am I" / active or stale work → `status`; create/update/close/search one issue → `issue-basics`; claim-then-prove ownership before mutating → `claim-safety`; drive one issue from plan to a merged PR under gates → `smith`; token-bounded state for the Hermes harness → `hermes-forge`.