Claude Skills by insideout-ai

github.com/insideout-ai

25 skillsA× 250 installs26 views

Domain NotificationsAOverdue-task reminder logic. Use when touching src/notifications/ or escalation rules.developmentVotes: 0GitHub stars: 12
Domain TasksATask creation, completion, and deletion logic and validation rules. Use when touching src/tasks/ or task status transitions.developmentVotes: 0GitHub stars: 12
Uc 01 Create TaskACreating a new task. Use when changing task-creation fields or validation.developmentVotes: 0GitHub stars: 12
Uc 02 Complete TaskAMarking an open task as done. Use when changing completion rules.developmentVotes: 0GitHub stars: 12
Uc 03 Receive Overdue ReminderAReceiving a reminder when a task becomes overdue. Use when changing reminder or escalation logic.developmentVotes: 0GitHub stars: 12
Uc 04 Delete TaskADeleting a task. Use when changing deletion rules.developmentVotes: 0GitHub stars: 12
Skills DirectorySkills Directory Look up any of 103,619 scanned skills — grade, score, and every finding. Free.Check a skill
Domain TasksATask creation and completion logic and validation rules. Use when touching src/tasks/ or task status transitions.developmentbackendVotes: 0GitHub stars: 12
Uc 01 Create TaskACreating a new task. Use when changing task-creation fields or validation.developmentVotes: 0GitHub stars: 12
Uc 02 Complete TaskAMarking an open task as done. Use when changing completion rules.developmentVotes: 0GitHub stars: 12
Uc 03 Receive Overdue ReminderAReceiving a reminder when a task becomes overdue. Use when changing reminder or escalation logic.developmentVotes: 0GitHub stars: 12
Domain DemoAExplains the fixture's small policy-decision domain.developmentVotes: 0GitHub stars: 12
Domain TasksATask creation and completion logic and validation rules. Use when touching src/tasks/ or task status transitions.developmentbackendVotes: 0GitHub stars: 12
Uc 01 Create TaskACreating a new task. Use when changing task-creation fields or validation.developmentVotes: 0GitHub stars: 12
Uc 02 Complete TaskAMarking an open task as done. Use when changing completion rules.developmentVotes: 0GitHub stars: 12
Close The GapsARefines a requirement into an AI-ready ticket: a Product Analyst session that fetches the ticket, loads project skills, explores affected code, asks gap-analysis questions in dependency-ordered batches, and outputs a Gherkin-format refined ticket. Supports an offline mode: export every question to a file to answer outside the session, then re-invoke with that file to inject the answers and resume. Use when refining a ticket before dev starts.developmentgoreactVotes: 0GitHub stars: 12
Define Test StrategyABootstraps a per-project test strategy file and an initial regression baseline once per project, the same way go-deep bootstraps the knowledge base — generating a starting test-strategy doc, scaffolding placeholder tests for confirmed-uncovered critical flows, and wiring a UC/domain test-tagging convention with a re-runnable coverage-check mode. Use when a project needs its test strategy and baseline coverage established after go-deep has already run.developmentpythongoVotes: 0GitHub stars: 12
ExecuteAImplements a plan `plan-the-work` produced, step by step: writes each step's code, re-runs that step's named test(s) to green with a 5-attempt retry limit before escalating, and applies the test-vs-product-behavior guardrail — halting the entire plan on a real product-behavior question rather than guessing. Once every step is green, runs `run-regression` as a completion gate. This is the execute step of the spec → plan-the-work → execute → review-the-pr pipeline. Use when implementing a plan ...developmentrustgoVotes: 0GitHub stars: 12
Find The ReposAGiven a ticket, shortlists which repositories in a multi-repo workspace it affects, by matching the ticket against each repo's product.md (falling back to architecture.md when the ticket is purely technical, with no business-logic content to match). Reports definite and possible matches, confirms the shortlist with the user — who may adjust it — then saves it. Use when you need to know which repo(s) a ticket belongs to, in a workspace with more than one repo, before refining or planning it.developmentgogitVotes: 0GitHub stars: 12
Go DeepAMakes any codebase AI-ready with a 3-tier doc system (CLAUDE.md, orientation maps, domain & UC skills). Use when onboarding a project to Claude Code or auditing/updating existing docs after the project evolves.developmentgotestingVotes: 0GitHub stars: 12
ImplementAOrchestrates the make-it-work pipeline for one ticket — context check → close-the-gaps → plan-the-work → execute → review-the-pr → final context sync — with saved, resumable workflow state, two autonomy levels (Guided, Autonomous), capped fix/replan loops, and local end-of-run workflow feedback. Never commits implementation changes, pushes, opens a PR, or uploads feedback. Use when taking a ticket from request to a reviewed, context-synced implementation in one run.developmentjavascriptpythonVotes: 0GitHub stars: 12
Plan The WorkATurns a spec or refined ticket into a concrete, execution-ready implementation plan — the plan-the-work step of the spec → plan-the-work → execute → review pipeline. Loads the project's skills, investigates the affected code across one or more repos, and writes an atomic, per-step plan file with no placeholders. When the target project has a test framework configured, it also writes and confirms per-step progression (red) and regression (currently-passing) tests. Use when planning how to impl...developmentgoexpressVotes: 0GitHub stars: 12
Review The PrAReviews a pull request in three documentation-grounded passes (business correctness, regression safety, coding standards) plus a docs-sync check, and emits an evidence-dense, verdict-first report. Use when reviewing a PR or diff in any repo that keeps CLAUDE.md plus uc-*/domain-* skills and .claude/rules docs.developmentrustgoVotes: 0GitHub stars: 12
Run RegressionARuns a project's regression suite — full or scoped to specific domains/use-cases — and reports pass/fail results; the shared implementation `execute` calls at the end of a plan. Use when running or checking a project's test suite, full or scoped to specific domains/use-cases.developmentgobashVotes: 0GitHub stars: 12
Shape The EpicATurns a rough idea into a complete, elaboration-ready epic via a guided interview session, PM-coach style. Use when writing or improving a product epic, drafting acceptance criteria, or documenting a feature for engineering.developmentgoshellVotes: 0GitHub stars: 12
Slice The EpicASlices a large requirement into small, AI-ready, value-driven slices. Use when the user asks to split, slice, right-size, or write stories from a requirement — including phrasing like "this ticket is too large," "break this into smaller pieces," or "help me write user stories for this epic."developmentgoVotes: 0GitHub stars: 12