One command for each phase of the backlog work: an idea, a request, or a bug to approved items. Each user story and bug gets acceptance criteria and a Gherkin Behaviour spec, a refine pass with the product owner, and a push to Jira, Azure DevOps, GitHub, GitLab, Linear, or files after approval. Research, a story map, and a prototype only for larger work. For product owners and business analysts.
Plugin product-flow from marketplace maikelsoft-skills in Charmedme/maikelsoft-skills. Commands read from the repo's manifest — today.
backlog-epicOld name of product-flow:epic. Use the skill product-flow:epic.
backlog-featureOld name of product-flow:feature. Use the skill product-flow:feature.
backlog-goalOld name of product-flow:product-goal. Use the skill product-flow:product-goal.
backlog-pushPuts a drafted backlog (goals, epics, features, user stories) into a ticket system after a duplicate check and the approval of the human. Use when a product owner or business analyst wants backlog items created in Jira, Azure DevOps, GitHub, GitLab, or Linear, or written to files when no ticket syst
backlog-storyOld name of product-flow:user-story. Use the skill product-flow:user-story.
bug-itemWrites one bug item for the backlog with a Gherkin bug spec - the rule that the bug breaks, what happens now, what must happen, and what must not change - ends with the refine pass, and puts it in the tracker after the approval of the product owner. Use when a product owner, a tester, or a developer
epicEpics for a product backlog with 3 levels (Epic, Feature, User Story). Use when a product owner or business analyst wants an epic written, rewritten, or reviewed, with its outcome, scope, and the features under it, for any ticket system. Ends with the refine pass and the push after approval.
example-mappingWrites examples.md, the example mapping file that dev-flow:plan-and-build 2.x reads. Use when dev-flow:plan-and-build asks for example mapping. For a person who wants an item refined, use product-flow:refine.
featureFeatures for a product backlog, with their user stories. Use when a product owner or business analyst wants a feature written, rewritten, or reviewed, with a goal, scope, acceptance criteria, and the stories under it, each with its Behaviour spec, for any ticket system. Ends with the refine pass and
idea-to-backlogOld name of product-flow:to-backlog. Use the skill product-flow:to-backlog.
product-goalProduct goals and sprint goals for a product backlog. Use when a product owner or business analyst wants a product goal or a sprint goal written, rewritten, or reviewed, with a measure and the backlog items that support it.
product-prototypeOld name of product-flow:prototype. Use the skill product-flow:prototype.
prototypeThrowaway clickable prototypes that test one product question before the backlog is written. Use when a product owner or business analyst wants to see a feature, a screen, or a flow, check that the team understood the request, or compare layout options, with the design system or branding of the team
refineMakes a draft backlog item ready to build - a review of the acceptance criteria and the Gherkin Behaviour spec, the open questions to the product owner in one message, and the approval - as a business analyst in a "three amigos" refinement. Searches the existing product decisions first. Use when a p
to-backlogTurns an idea, a feature request, or a bug report into the backlog items that it needs - an epic, features, user stories, or a bug item - each story and bug with its acceptance criteria and Gherkin Behaviour spec, with the refine pass and a push after the approval of the product owner. Sets the dept
user-storyWrites, reviews, or splits user stories (also called PBIs or requirements) with acceptance criteria and a Gherkin Behaviour spec, ends with the refine pass, and puts each story in the tracker after the approval of the product owner. Use when a product owner or business analyst wants a user story wri
Stack skills for a .NET 10 team with an Angular front end: C#, ASP.NET Core, OpenAPI, validation, EF Core, SQL Server, PostgreSQL, MSTest 4, analyzers, observability, Redis, Elasticsearch, RabbitMQ, Wolverine, MailKit, PuppeteerSharp, Angular, secure coding, and the move to AwesomeAssertions. Version-specific rules, a check step with a tool, and one report format.
19 skills
/ux-design designs one item with UI before the build: problem frame, flow, pattern rules, design spec with a source for each decision, states, mockups, and a prototype for a test with users. /ux-review checks the built screens against the design. A UX designer agent does the work. Also Claude Design, Figma, and OpenPencil, brand files and DTCG tokens, and WCAG 2.2 accessibility.
13 skills · 1 agent
The team mode of dev-flow for one large or risky work item: a senior designs and builds the core, mediors build work packages, a security reviewer checks the diff, and the main session leads with the plan gate and the final gate. Same spec.md, locked tests, and run.md header as a solo build. Needs dev-flow 3.1.0 or later and dev-stack.
7 skills · 4 agents · hooks
Write, rewrite, and review developer documentation: README, tutorial, how-to, reference, explanation, ADR, changelog, code comments, and UI text. /update-docs checks and updates the whole doc set of a project.
11 skills
Builds one work item (story, bug, task, or chore) from its ticket to tested commits, spec first. Copies the Behaviour spec of the ticket and locks one test file for each rule. Builds one scenario at a time with TDD. Proves the result with held-back tests, a mutation check, and fresh reviews. Sets the size from the change and the risk. Product questions go back to the product owner on the ticket.
2 skills · hooks
Build good agent skills and agents: research, concept, test, build. Skills build-skill and build-agent, with checkers. Agents for Claude Code, the Agent SDK, Managed Agents, and OpenClaw.
2 skills
Talk like caveman. Cut filler. Keep technical details explicit.
22 skills · 1 command · 3 agents · hooks
Persistent memory for Claude Code: the next session starts where the last one left off.
29 skills · 1 MCP server · hooks
tasteskill 2.5.1: professional company websites at the figma.com and x.ai level, with one section per screen, real photographs, real product UI, effects kept for tech and gaming pages, and a real-browser checker and finish gate.
1 skill
Open-source AI job search that runs locally in your AI coding CLI: scan job portals, evaluate listings into a structured A-H report with a 1-5 score, tailor your CV, track applications
5 skills · hooks
Cross-session memory and token savings for coding agents.
6 skills · 1 agent · 1 MCP server · hooks
Package any website or local web build into a lightweight desktop app with Pake CLI.
1 skill
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.