ai-driven-dev

@ai-driven-dev source repo

94 skills
0 followers
9 hours ago last updated

▌
03 Context Generate 2 · ai-driven-dev bundle
Context Generate

0
installs
▌
Plan · ai-driven-dev
Split a request into independent tasks, one worktree each

0
installs
▌
Harden · ai-driven-dev
Re-read a diff for unvalidated input, swallowed errors and missing edge cases

0
installs
▌
Check Task · ai-driven-dev
Run the project assertions and return a binary verdict

0
installs
▌
Rollback · ai-driven-dev
Roll back a release of the ingest platform without losing in-flight batches. Use when a deploy has to be undone.

0
installs
▌
Add Endpoint · ai-driven-dev
Procedure — add an endpoint

0
installs
▌
Schema Migration · ai-driven-dev
Procedure — schema migration

0
installs
▌
Migrate External API · ai-driven-dev
Phased migration of a third-party API client — new client alongside the old, reads before writes, a disagreement metric before cutover. Use when replacing or upgrading a provider SDK.

0
installs
▌
Test · ai-driven-dev bundle
Holds the two testing disciplines this package learned by paying for them, and points at the rest. Use when writing or changing a test under tests/, touching a golden snapshot, or fixing a user-reported bug. Do NOT use for tier conventions, the vitest projects, doubles, fixtures or how to run a suite — those live in `aidd_docs/memory/testing.md`. Do NOT use for writing production code — use the context skill that owns the concept (`tools`, `translate`, `distribution`, `framework`, `telemetry`).

0
installs
▌
Tools · ai-driven-dev bundle
Defines or modifies what the project targets, under src/contexts/tools/ — an AI/IDE tool profile, its build contract, the content-translation capability classes it composes (agents/skills/commands/rules/hooks), and its own native-plugin adapter. Use when adding a new AI or IDE tool, changing a tool's Has* capability intersection, adding or modifying a capability class, or declaring a tool's `aidd translate` build contract. Do NOT use for the canonical-to-native translation pipeline itself — use `translate`. Do NOT use for where plugin content comes from — use `distribution`. Do NOT use for manifest or install orchestration — use `framework`.

0
installs
▌
Framework · ai-driven-dev bundle
Owns the installation record and everything done to a project, under src/contexts/framework/ — the manifest aggregate, and the setup/install/restore/uninstall/doctor orchestration built on top of it. This is the only context allowed to reach `translate` and `distribution`; `tools` is reachable from `telemetry` too. Use when adding a use-case that touches the manifest, a setup/doctor/sync/uninstall flow, a new top-level CLI orchestration, or a launcher that runs an external binary (kanban-shaped). Do NOT use for a tool's own profile or capability classes — use `tools`. Do NOT use for the translation pipeline — use `translate`. Do NOT use for where content is fetched from — use `distribution`.

0
installs
▌
Telemetry · ai-driven-dev
Owns what a session cost and who it was for, under src/contexts/telemetry/ — reading a tool's own local files, attributing a figure to a person, a task, a flow or a step, and the sink that keeps records per machine. Use when adding a reader for another tool's transcript format, changing how a figure is attributed or reported, touching the sink or the identity store, or wiring a telemetry port. Do NOT use for what a tool declares about being measured — that is `kernel/measurement.ts`, read via the `tools` skill. Do NOT use for installing or removing the hook that writes the run journal into a project — that record belongs to `framework`.

0
installs
▌
Translate · ai-driven-dev
Builds the canonical-source-to-target-native translation pipeline under src/contexts/translate/ — target-aware content transforms, the plugin content translator, and the build strategies behind `aidd translate` and `aidd sync`. Use when adding a target-aware transform, changing `PluginContentTranslator`, adding a build strategy, or wiring a new tool into the build registry. Do NOT use for a tool's own profile, capability classes, or build contract — use `tools`. Do NOT use for where content is fetched from — use `distribution`. Do NOT use for manifest/install orchestration — use `framework`.

0
installs
▌
03 Prd · ai-driven-dev bundle
Generate a structured Product Requirements Document from a need, idea, or brainstorm, confirmed before save. Use when the user wants to draft or generate a PRD or product requirements. Not for user stories or a technical plan.

0
installs
▌
04 Spec · ai-driven-dev bundle
Generate or refine a spec, a feature's immutable contract, from a request, a PRD, or review findings. Use when the user wants to draft or refine a spec. Not for writing code, a full PRD, or changing a locked spec.

0
installs
▌
07 Epic · ai-driven-dev bundle
Produces or refines an outcome-based Epic for a product backlog. Use when the user wants to frame, review, resume, or persist an Epic. Not for Product Briefs, User Stories, or implementation.

0
installs
▌
10 Task · ai-driven-dev bundle
Produces or refines a backlog Task for bounded delivery work without independent user value. Use when the user wants to create, link, order, estimate, transition, or complete one. Not for User Stories, Spikes, Defects, or implementation.

0
installs
▌
Distribution · ai-driven-dev
Owns where plugin and marketplace content comes from and how it is fetched, under src/contexts/distribution/ — marketplace registration, catalog parsing, and the ports/adapters that reach git and HTTP. Use when adding a new marketplace source kind, a catalog parser for a foreign format, or a fetch/cache/trust-store adapter. Do NOT use for what a tool does with fetched content — use `tools` or `translate`. Do NOT use for recording what got installed on a project — use `framework`.

0
installs
▌
01 Plan · ai-driven-dev bundle
Turn a request, ticket, or file into a phased implementation plan. Use to plan a feature before building, or to turn a ticket into phases. Do NOT use to write code or review a diff.

0
installs
▌
06 Test · ai-driven-dev bundle
Write and iterate tests until they pass, or validate a user journey end to end in the browser. Use when the user wants to add coverage, find what's untested, or walk a flow. Not for auditing test health or debugging a failure.

0
installs
▌
10 Todo · ai-driven-dev bundle
Split the user prompt into independent todos and run one executor agent per todo in parallel, then report a minimal table. Use when the user says "todo" or asks to fan out a multi-part request into parallel implementations.

0
installs
▌
05 Spike · ai-driven-dev bundle
Produces an evidence-bounded spike for an uncertainty blocking estimation, feasibility, or design. Use when the user wants to frame, investigate, resume, or conclude one. Not for general research or implementation.

0
installs
▌
01 Hello · ai-driven-dev bundle
Smoke-test that confirms the aidd-ui plugin loads. Use when the user wants to verify the alpha aidd-ui plugin is installed and reachable. Not for real UI or UX design work.

0
installs
▌
04 Audit · ai-driven-dev bundle
Audit a codebase read-only across seven quality pillars into one ranked report. Use when the user wants to assess, health-check, or audit a codebase or one pillar. Not for fixing findings, reviewing a change, or checking a feature works.

0
installs
▌
08 Debug · ai-driven-dev bundle
Reproduce and fix a known bug, or find an unknown root cause by hypothesis validation. Use when the user wants to fix a bug, find why something breaks, or reopen a stuck investigation. Not for building a feature or reviewing a diff.

0
installs
▌
09 Defect · ai-driven-dev bundle
Produces or refines a backlog Defect from an observed product mismatch. Use when the user wants to report, assess, link, order, transition, or verify a defect. Not for incident response, debugging, or implementation.

0
installs
▌
03 Assert · ai-driven-dev bundle
Assert the work behaves by iterating the project's coding assertions until they pass, plus optional architecture and frontend facets. Use to validate an implementation. Not for reviewing or writing tests.

0
installs
▌
05 Review · ai-driven-dev bundle
Review a diff read-only on three axes, code, behavior versus the plan, and relevancy, into one verdict report. Use before shipping a change. Not for fixing findings or auditing a codebase.

0
installs
▌
01 Commit · ai-driven-dev bundle
Create an atomic git commit with a conventional message, optionally pushing. Use when the user wants to commit changes, optionally pushing the branch. Not for amending, rebasing, opening a pull request, or tagging a release.

0
installs
▌
12 Cook · ai-driven-dev bundle
Manage project recipes/how-to sheets by listing, creating, updating, researching, or applying a recipe. Use for recipe, cook, /cook, list, new, update, research, apply.

0
installs
▌
07 Refactor · ai-driven-dev bundle
Improve code across four axes (cleanup, performance, security, architecture) by scanning and fixing, or applying a pushed audit report. Use when the user wants to refactor, optimize, harden, or remove code. Not for read-only diagnosis or adding tests.

0
installs
▌
09 For Sure · ai-driven-dev bundle
Run an iterative agent loop that retries until a runnable success condition passes. Use when the user says "for sure", "keep trying until", or wants guaranteed completion against a success command. Not for one-shot tasks or uncheckable goals.

0
installs
▌
10 Learn · ai-driven-dev bundle
Capture durable project learnings. Use when the user wants to remember, record, or formalize a decision, convention, lesson, pitfall, reusable workflow, or review finding. Not for preferences or temporary notes.

0
installs
▌
02 Implement · ai-driven-dev bundle
Write an existing plan's code, phase by phase, until every acceptance criterion holds. Use when a plan exists and needs implementing. Do NOT use to write a plan, review a diff.

0
installs
▌
00 Repo Init · ai-driven-dev bundle
Initialize a project repository with git init, a default branch, a bootstrap commit, CONTRIBUTING.md, and optionally the remote. Use when the user wants to init or set up a new repo, or publish to a remote. Not for committing, opening a PR, or tagging.

0
installs
▌
11 Browser QA · ai-driven-dev bundle
Run post-review browser QA and produce short named videos for a locked happy path and sourced browser edge cases. Use when the user wants concise reviewer evidence for a web journey. Not for API, CLI, automated tests, diff review, or application fixes.

0
installs
▌
01 Ticket Info · ai-driven-dev bundle
Retrieve and display a ticket from the configured ticketing tool. Use when the user wants to see, show, or look up a ticket's details. Not for creating a ticket, or commenting on, transitioning, or reassigning one.

0
installs
▌
00 Init · ai-driven-dev bundle
Turns AIDD measurement on for a project, proves it is recording, lets a person opt into (or out of) naming themselves on their own records, and removes what was measured when asked. Use when the user wants to start measuring what their work costs, wants to stop, asks why nothing is being recorded, wants their own name to appear on (or disappear from) what gets measured, or wants their measured data deleted. Not for answering what a piece of work consumed.

0
installs
▌
01 Cost · ai-driven-dev bundle
Answers what a period or one task consumed - a total, a day-by-day series, or a breakdown by step, model, task, backlog item, orchestrated flow, tool, project or person - and hands back the artefact each question deserves. Use when the user asks what a piece of work cost, what changed, where the effort went, which task, which backlog item or ticket, which orchestrated run, for which project, or who spent it. Not for turning measurement on.

0
installs
▌
00 Onboard · ai-driven-dev bundle
Guide a project's journey through AIDD, from first setup to shipping a feature. Use when the user says onboard me, where do I start, or what to do next. Not for listing every installed surface.

0
installs
▌
09 Mermaid · ai-driven-dev bundle
Generate a valid Mermaid diagram from a written source through a plan, generate, review loop. Use when the user wants to turn an architecture, lifecycle, or flow into a Mermaid diagram. Not for other diagram formats or image rendering.

0
installs
▌
11 Explore · ai-driven-dev bundle
Explore the current project across its tooling, context, and codebase. Use to survey what is installed, see what is available, or find which skill, agent, or rule fits a goal. Not for choosing the next step or running an item; it only points.

0
installs
▌
02 User Stories · ai-driven-dev bundle
Produces or refines ordered User Stories from an Epic, Product Brief, PRD, or bounded request. Use when the user wants to slice, write, assess, order, or persist Stories. Not for Epics or implementation.

0
installs
▌
08 Three Amigos · ai-driven-dev bundle
Assesses an Epic or Story through one product, delivery, or quality lens, then reconciles three caller-supplied reports. Use when the user wants to refine one before a backlog change. Not for spawning or writing.

0
installs
▌
02 Check · ai-driven-dev bundle
States what is in place — where measurement is allowed from, whether an identity is attached, where records land, whether the recorder is declared — then answers whether AIDD measurement is actually recording, one independently verifiable line per claim. Use when the user doubts a figure, sees no run file appear, wants proof the chain is working, or wants to know what is already configured. Not for turning measurement on or answering what a period cost.

0
installs
▌
03 Release Tag · ai-driven-dev bundle
Cut a semver release with an annotated tag and release notes. Use when the user wants to release, tag a release, bump the version, or cut a version. Not for a plain commit, a pull request, or amending an existing tag.

0
installs
▌
06 Product Brief · ai-driven-dev bundle
Produces a concise Product Brief before requirements. Use when the user wants to frame or revisit a product opportunity and how it will be validated. Not for requirements, technical design, or planning.

0
installs
▌
02 Challenge · ai-driven-dev bundle
Rethink just-completed work against an agreed plan, classifying findings as deal-breaker, suggestion, or correct, with a confidence score. Use to challenge or critically review recent work. Not for line-by-line style review or writing code.

0
installs
▌
02 Pull Request · ai-driven-dev bundle
Create a draft pull or merge request from the current branch, in whatever VCS tool the project uses. Use when the user wants to open a pull or merge request. Not for committing, pushing, or merging a branch.

0
installs
▌
04 Issue Create · ai-driven-dev bundle
Create an issue in the configured ticketing tool. Use when the user wants to file a bug, open an issue, or report a problem. Not for committing, opening a pull request, or commenting on an existing issue.

0
installs
▌
01 Bootstrap · ai-driven-dev bundle
Design and validate a new SaaS's architecture into an INSTALL.md via Q&A and stack comparison. Use when the user starts a project, chooses a stack, or picks an architecture pattern. Not for editing an existing stack or scaffolding code.

0
installs
▌
01 Sdlc · ai-driven-dev bundle
Autonomously orchestrates a request from framing to a draft pull request, isolating implementation, independent review, and final outcome challenge. Use when the user wants to deliver a change end to end. Not for running one development step.

0
installs
▌
01 Brainstorm · ai-driven-dev bundle
Clarify a vague product or technical intent through natural discovery. Use when the user has a half-formed idea, ambiguous request, or asks to brainstorm, discover, refine, or clarify. Not for artifact gap scans, planning, or code.

0
installs
▌
04 Fact Check · ai-driven-dev bundle
Verify factual claims in a text against authoritative sources and rewrite it with footnote citations, hedging the unconfirmed. Use to fact-check, verify a claim, or cite sources on request. Not for judging code or clarifying requirements.

0
installs
▌
03 Shadow Areas · ai-driven-dev bundle
Scan a markdown artifact (idea, stories, PRD, spec) for blind spots into a shadow report grouped by category and severity. Use to find gaps or what is missing in a written artifact. Not for interactive Q&A or code review.

0
installs
▌
02 Backlog · ai-driven-dev bundle
Orchestrates a product backlog end to end. Use when the user wants to ask what it holds, or to run intake, triage, refinement, review, lifecycle events, ordering, health checks, or repair. Not for one known artifact step.

0
installs
▌
05 Rule Generate · ai-driven-dev bundle
Generate a coding rule that governs editor and agent behavior across the host AI tools. Use when the user wants to write, add, or refactor a rule, convention, or coding standard. Not for other artifacts like skills, agents, or hooks.

0
installs
▌
08 Hook Generate · ai-driven-dev bundle
Generate a hook, a handler that runs at a lifecycle event, across the host AI tools. Use when the user wants to create, scaffold, or refactor a hook, or automate an action at a lifecycle point. Not for other artifacts like skills or rules.

0
installs
▌
02 Project Memory · ai-driven-dev bundle
Build the project's memory of its architecture, conventions, and decisions, and wire it into your AI tools. Use when the user wants to set up or refresh project memory, or rewire it into a tool. Not for editing one existing memory file.

0
installs
▌
04 Skill Generate · ai-driven-dev bundle
Generate a router-based skill across the host AI tools a project uses. Use when the user wants to create, scaffold, or refactor a skill, or turn a workflow into one. Not for other artifacts like rules, agents, commands, hooks.

0
installs
▌
06 Agent Generate · ai-driven-dev bundle
Generate an agent across the host AI tools a project uses. Use when the user wants to create, scaffold, or refactor an agent, subagent or specialized role. Not for other artifacts like skills, rules, commands, hooks.

0
installs
▌
00 Async Dev · ai-driven-dev bundle
Drive the async-dev pipeline from one entry point, whether setup, run, or review. Use when the user wants to install async dev, run a ready issue, or address PR review comments, or on a webhook trigger. Not for plain status checks.

0
installs
▌
03 Context Generate · ai-driven-dev
Route a request to generate a context artifact (skill, rule, agent, command, or hook) to its generator when the kind is unnamed. A named kind triggers its generator directly. Not for listing existing artifacts.

0
installs
▌
07 Command Generate · ai-driven-dev bundle
Generate a flat slash command across the host AI tools a project uses. Use when the user wants to create, scaffold, or refactor a one-shot slash command. Not for multi-step skills or other artifacts like rules, agents, hooks.

0
installs
▌
Aidd Pm 03 Prd · ai-driven-dev bundle
Generate a Product Requirements Document from a feature description or user stories.

0
installs
▌
Aidd Pm 05 Spec · ai-driven-dev bundle
Generates and refines a project spec from a free-form human request. The spec is the immutable target a planner consumes. Use when starting a new run, when an existing spec needs refinement after review, or when a human wants to draft a spec collaboratively.

0
installs
▌
Aidd Dev 00 Sdlc · ai-driven-dev
Pure orchestrator for the full AIDD development flow. Use when a human (or Gardener) needs to take a free-form request from idea to shipped code, end-to-end. Coordinates spec generation, planning, implementation, and review by composing other skills and agents. Holds no business logic of its own — every step is delegated.

0
installs
▌
Aidd Dev 01 Plan · ai-driven-dev bundle
Generate technical implementation plans, define component behaviors, and extract design details from images.

0
installs
▌
Aidd Dev 05 Test · ai-driven-dev bundle
Write and iterate on tests until they pass, and validate user journeys end-to-end in the browser.

0
installs
▌
Aidd Dev 03 Audit · ai-driven-dev bundle
Perform deep codebase analysis to identify technical debt, dead code, and improvement opportunities.

0
installs
▌
Aidd Dev 07 Debug · ai-driven-dev bundle
Reproduce and fix bugs systematically using test-driven workflow, root cause analysis, and hypothesis validation.

0
installs
▌
Aidd Dev 02 Assert · ai-driven-dev bundle
Assert features work as intended — general assertions, architecture conformance, and frontend UI validation.

0
installs
▌
Aidd Dev 04 Review · ai-driven-dev bundle
Review code quality against project rules and validate feature behavior against plan specifications.

0
installs
▌
Aidd Pm 04 Clarity · ai-driven-dev
Ultra-compressed communication mode. Cuts token usage ~75% while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra. Toggle on/off by invoking /clarity again. Use when user says "clarity", "less tokens", "be brief", or invokes /clarity.

0
installs
▌
Aidd Vcs 01 Commit · ai-driven-dev bundle
Create an atomic git commit with conventional message format. Supports interactive mode (human-driven, may split commits, asks approval) and auto mode (agent-driven, no approval, single commit). Use when the user says "commit", "git commit", "create a commit", "commit my changes", "commit and push", or invokes `/commit`. Do NOT use for amending existing commits, force-pushing, rebasing, opening pull requests, or release tagging.

0
installs
▌
Aidd Dev 06 Refactor · ai-driven-dev bundle
Optimize code for performance and fix security vulnerabilities following OWASP guidelines.

0
installs
▌
Aidd Dev 08 For Sure · ai-driven-dev bundle
Iterative agent loop that tracks attempts and retries until a success condition is met. Use when the user says "for sure", "make sure", "keep trying until", "loop until done", "don't stop until", or needs guaranteed completion of a task with explicit success criteria.

0
installs
▌
02 Run · ai-driven-dev bundle
Run

0
installs
▌
Aidd Context 05 Learn · ai-driven-dev bundle
Capture and store learnings from recently implemented features into memory bank, decisions, or coding rules.

0
installs
▌
Aidd Pm 01 Ticket Info · ai-driven-dev bundle
Retrieve and display ticket information from the project's configured ticketing tool.

0
installs
▌
Aidd Async Dev 01 Setup · ai-driven-dev bundle
Installs and configures the aidd-async-dev plugin in a target repo. Use when the user runs "/setup async dev", "configure async dev", "install async-dev plugin", or asks to set up Claude auto-implementation on issues. Do NOT use for running the async pipeline (use `aidd-async-dev:02:run`) or handling PR review loops (use `aidd-async-dev:03:review`).

0
installs
▌
Aidd Context 04 Mermaid · ai-driven-dev bundle
Generate high-quality Mermaid diagrams from markdown content using a structured plan-validate workflow.

0
installs
▌
Aidd Refine 03 Condense · ai-driven-dev bundle
Toggle terse output mode with intensity levels (lite, full, ultra) so prose drops articles, filler, and pleasantries while code, quoted errors, and security warnings stay verbatim. Use when the user says "condense", "condense output", "be more concise", "shorter answers", "tighten output", "/condense", "/condense full", "/condense ultra", or "stop condense". Do NOT use for editing existing prose, summarizing a long document, or compressing source code (only output style is affected, not content).

0
installs
▌
Aidd Vcs 03 Release Tag · ai-driven-dev bundle
Cut a semver release by computing the next version from recent commits, generating annotated release notes from the template, validating with the user, then creating and pushing the git tag along with a bump commit. Use when the user says "release", "tag", "tag this release", "bump version", "release v1.2.0", "cut a release", or invokes `/release-tag`. Do NOT use for plain commits without a tag, opening pull requests, pushing a branch only, or amending existing tags.

0
installs
▌
Aidd Async Dev 03 Review · ai-driven-dev bundle
Handles the post-PR review-fix loop for runs created by this plugin's run skill. Collects review comments, decides whether to keep iterating, delegates fixes to whichever SDLC capability is loaded at runtime, and finalizes when stop conditions trigger. Use when the user (or a webhook / cron) says "handle review comments", "iterate on PR <n>", "address review feedback automatically", or invokes this skill on a specific PR. Do NOT use for the initial implementation or for setup; other skills in this plugin cover those.

0
installs
▌
Aidd Refine 02 Challenge · ai-driven-dev bundle
Rethink prior work to verify correctness against an agreed plan, classifying findings as deal-breakers, suggestions, or correct, with a confidence score. Use when the user says "challenge this", "rethink your plan", "is this correct", "review my last decision", "challenge my decision", "challenge what you did", "is my decision right", "criticize this", "find flaws", or asks for a critical review of just-completed work. Do NOT use for line-by-line code review against a style guide, implementing features, writing tests, or generating new code.

0
installs
▌
Aidd Vcs 02 Pull Request · ai-driven-dev bundle
Create a draft request from the current branch by detecting the base branch, filling the team template, and asking the user to validate before opening. The configured VCS tool is invoked transparently. Use when the user says "open a pr", "open a pull request", "create a pr", "create a merge request", "open mr", "draft a pr for this branch", or invokes `/pull-request`. Do NOT use for committing changes, pushing a branch directly, tagging releases, merging an existing request, or amending commits.

0
installs
▌
Aidd Vcs 04 Issue Create · ai-driven-dev bundle
Create a tracker issue with the configured ticketing tool by gathering a thorough problem description, filling the team template, validating with the user, then opening it. Use when the user says "new issue", "create an issue", "file a bug", "file an issue", "report bug", "open an issue", or invokes `/issue-create`. Do NOT use for committing changes, opening pull requests, tagging releases, or commenting on existing issues.

0
installs
▌
Aidd Context 01 Bootstrap · ai-driven-dev bundle
Imagine and validate the technical architecture of a new SaaS through interactive Q&A, candidate-stack comparison, multi-agent audit, and an INSTALL.md output. Use when starting a new SaaS project, choosing a stack, designing the architecture pattern (monolith vs microservices vs serverless), or producing a project's INSTALL.md. Do NOT use for editing an existing project's stack (use direct edits or `aidd-dev:01:plan`), database schema design, or scaffolding actual files (this skill produces docs only, no code).

0
installs
▌
Aidd Context 06 Discovery · ai-driven-dev bundle
Help users discover installed skills and find the right one for their use case.

0
installs
▌
Aidd Refine 01 Brainstorm · ai-driven-dev bundle
Interactive brainstorming session to clarify and refine requests through iterative questioning. Use when user mentions unclear requirements, vague ideas, or needs clarification on features. Do NOT use for clear technical specs, implementation details, or when requirements are already well-defined.

0
installs
▌
Sample · ai-driven-dev bundle
Sample skill for testing reference rewriting.

0
installs
▌
Aidd Context 02 Project Init · ai-driven-dev bundle
Initialize or refresh the project memory bank, scaffold the rules directory, and ensure AI context files contain the project memory block. Use when running `aidd init` for the first time, bootstrapping a new project, or re-running the init flow on an existing project. Do NOT use for updating individual memory files after they exist - use `aidd-context:05:learn` instead; do NOT use for editing a single rule - edit the file directly.

0
installs
▌
Aidd Pm 02 User Stories Create · ai-driven-dev bundle
Generate well-structured user stories from feature requirements through iterative Product Owner questioning.

0
installs

94 published skills