All authors
Claude Skills by marin-ai-tech
github.com/marin-ai-tech19 skills0 installs0 views
- AdoptPrepare an existing project for agents - check the layout, adapt or scaffold the documents, fill them from the code, and draft the sdlc settings and roles for a person to apply.Votes: 0GitHub stars: 3
- ArchiveClose a completed SDLC change - confirm every required gate is satisfied, merge its delta specs into the living specs via OpenSpec archive, and capture learnings (evals, CLAUDE.md/AGENTS.md rules, follow-up intents). Use when the user asks to archive, finish, or close a change.Votes: 0GitHub stars: 3
- BacklogSee the backlog, decompose an epic or an idea into items, bring an item to ready and start it - always through the sdlc backlog commands.Votes: 0GitHub stars: 3
- BuildImplement an SDLC change from its approved plan (Stage 3, Build) with a continuous feedback loop - work through tasks.md, run the project's checks after each step, keep plan.md in sync. Use when the plan gate is approved and the user asks to implement, build, or apply the change.Votes: 0GitHub stars: 3
- ConfigPropose a settings or roles change for a person to review and apply.Votes: 0GitHub stars: 3
- ExploreResearch and pressure-test an idea before deciding whether to write intent.Votes: 0GitHub stars: 3
- GuideExplain how to work with sdlc in this project - stages, gates and approvals, roles, tracks, bug fixes, the backlog, rework and takeover, verification, review, MCP, configuration, and why the hook denied something. Use when the user asks how sdlc works, how to do something with it, what a term means, which command a person runs, or why an action was refused.Votes: 0GitHub stars: 3
- HealthReview the health of the project's process and practices - waits on people, stalled changes, rework reasons, first-pass verification, waivers, hook denials, configuration gaps - and draft improvements as backlog items for a person to order. Use when the user asks how the process is going, why things are slow, what to improve, or after a release or retrospective.Votes: 0GitHub stars: 3
- HelpShow available SDLC workflows and the current project state.Votes: 0GitHub stars: 3
- IntentCapture an idea, request, ticket or problem as intent.md, the Stage 1 (Plan) artifact of the AI-native SDLC, for product-owner approval. Use when the user describes something they want built or fixed, or says \"new idea\", \"capture intent\", \"start a change\".Votes: 0GitHub stars: 3
- NextAdvance an SDLC change to its next step in the AI-native lifecycle (intent, spec, plan, build, verify, review, release, archive). Use when the user says \"continue\", \"next step\", \"what's next\", or wants to move a change forward without naming the stage.Votes: 0GitHub stars: 3
- PlanProduce the implementation plan (Stage 3, Build) from an approved spec - plan.md (files that change, order of work, risks, proof, rollback) and tasks.md - for engineer approval before any code is written. Use after the spec gate is approved or when the user asks for an implementation plan.Votes: 0GitHub stars: 3
- ReleasePrepare an approved SDLC change for release (Stage 5, Deploy) - release.md with changelog, per-environment rollout, monitoring signals and a rehearsed rollback - up to the production gate, which a release manager authorizes. Use when the user asks to release, ship, or deploy a change.Votes: 0GitHub stars: 3
- ReviewReview a verified SDLC change (Stage 5, Deploy) in independent passes - bugs, security, compliance with the spec, plan and design principles in REVIEW.md - record severity-ranked findings in review.md, fix the important ones, and hand off to a human code owner. Use when the user asks for a review, a PR review, or to address review findings.Votes: 0GitHub stars: 3
- SpecTurn an accepted intent into the requirements and design spec (Stage 2, Design) - OpenSpec proposal.md, delta specs and design.md with policies applied and areas of concern flagged. Use after the intent gate is approved, or when the user asks to write or refine requirements or the design.Votes: 0GitHub stars: 3
- StatusShow the SDLC dashboard - every active change with its stage (plan, design, build, test, deploy), gate states, approvals, verification and review status, and who must act next. Use when the user asks for status, progress, what is blocked, or what needs approval.Votes: 0GitHub stars: 3
- TeamSet up the agent team of this project - bring the roles (analyst, architect, developer, tester, reviewer) from the team registry or the built-in set, and draft the project's own rules into each role from the code, or from the idea of an empty project, for a person to accept. Use when the user starts a project, asks for agent roles, or wants the roles adapted to the project.Votes: 0GitHub stars: 3
- TriageClose the loop (Stage 6, Maintain) - turn an alert, incident, failing build, security finding or ticket into a diagnosed, evidence-backed intent.md that re-enters the lifecycle. Use when the user pastes an alert, incident, error report or scan finding, or asks to investigate a production problem.Votes: 0GitHub stars: 3
- VerifyVerify an implemented SDLC change (Stage 4, Test) - run the project's checks with `sdlc verify` to record literal evidence, then get an independent behavioral verification against the spec scenarios in a fresh context. Use after implementation, or when the user asks to test, verify, or check that a change works.Votes: 0GitHub stars: 3