File one new ticket in the project's issue tracker. Use this skill when work needs recording where the team tracks it, rather than only inside AID. Describe the ticket in free text; flags let you name the connector, the level (epic, story or task) and a parent. It resolves which tracker to use, composes the payload…
Create a UI component or page. Use this skill when you already know what to create and want it scoped, specified, and broken into reviewable tasks in a single pass, with no requirements interview. You approve the resulting plan before anything is built: this skill plans and stops, so run /aid-execute to carry the plan…
Create a new internal code artifact (module, interface, type) from scratch. Use this skill when you already know what to create and want it scoped, specified, and broken into reviewable tasks in a single pass, with no requirements interview. You approve the resulting plan before anything is built: this skill plans and…
Decompose approved requirements into discrete features, each recorded as a ### Feature NNN section of REQUIREMENTS.md § 11 that cites the AC-N criteria it claims. Use this skill once /aid-describe has produced an approved REQUIREMENTS.md and the work needs splitting into features before any one of them is specified.…
Package completed deliveries into a release. Use when deliveries are complete and ready to ship. It selects the eligible deliveries, verifies the combined build, packages according to the project's own infrastructure, generates the release notes, and updates each artifact's status.
Deprecate an existing artifact/API: mark deprecated, add warnings and a migration path, without deleting yet. Use this skill when you already know what to deprecate and want it scoped, specified, and broken into reviewable tasks in a single pass, with no requirements interview. You approve the resulting plan before…
Gather requirements through an adaptive interview and write them to REQUIREMENTS.md. Use this skill when you know roughly what you want built but the scope, the users, and the acceptance criteria are not yet pinned down. It asks one question at a time, each chosen by a seasoned-analyst elicitation engine that picks…
Develop an API design as a DESIGN SEED in .aid/design/api.md -- the resource shape, the request/response contract, and the error model. Use this skill when an endpoint's shape is still being worked out and you want the contract settled before anyone writes the handler. Grounded in the Knowledge Base (.aid/knowledge/)…
Develop the system's shape as a DESIGN SEED in .aid/design/architecture.md -- components, boundaries, interactions, invariants, and what is deliberately not a component. Use this skill when how the system should be shaped is still being worked out, and you want that thinking captured before it is written into the…
Develop the defined-and-prioritized item set as a DESIGN SEED in .aid/design/backlog.md -- item definitions, done-conditions, priorities, and which tech-debt.md rows the user is accepting into the plan. Use this skill when what belongs in the backlog is still being decided, and you want that thinking captured as a…
Develop the delivery pipeline as a DESIGN SEED in .aid/design/cicd.md -- stages, triggers, environments, promotion, and release flow. Use this skill when how the project should be built, gated and shipped is still being worked out. Grounded in the Knowledge Base (.aid/knowledge/) and the project source. It WRITES NO…
Develop a CLI design as a DESIGN SEED in .aid/design/cli.md -- the command and subcommand shape, its arguments and flags, and its output and error conventions. Use this skill when a command's signature and output are still being worked out. Grounded in the Knowledge Base (.aid/knowledge/) and the project source. It…
Develop a configuration-option or feature-flag design as a DESIGN SEED in .aid/design/config.md -- the option or flag, its default and scope, and how it is read. Use this skill when a new option's shape, default and blast radius are still being worked out. Grounded in the Knowledge Base (.aid/knowledge/) and the…
Develop a dashboard / BI-view design as a DESIGN SEED in .aid/design/dashboard.md -- the data source, the visualizations, and the refresh cadence. Use this skill when what a dashboard should show, and to whom, is still being decided. Grounded in the Knowledge Base (.aid/knowledge/) and the project source. It WRITES NO…
Develop a data-model design as a DESIGN SEED in .aid/design/data-model.md -- its entities, their relationships, and the migration impact of introducing them. Use this skill when an entity's shape and its relationships are still being worked out, before any migration is written. Grounded in the Knowledge Base…
Develop a data-pipeline design as a DESIGN SEED in .aid/design/data-pipeline.md -- the source, the transform, the sink, and the schedule. Use this skill when where the data comes from, what happens to it, and where it lands are still open questions. Grounded in the Knowledge Base (.aid/knowledge/) and the project…
Develop a document design as a DESIGN SEED in .aid/design/document.md -- the document's kind and structure, its audience, and its placement. Use this skill when a document's angle, audience and shape are still being worked out, before it is drafted. Grounded in the Knowledge Base (.aid/knowledge/) and the project…
Develop an infrastructure-resource design as a DESIGN SEED in .aid/design/infra.md -- the resource, its configuration, and its provisioning and teardown. Use this skill when a resource's shape and access policy are still being worked out, before anything is provisioned. Grounded in the Knowledge Base (.aid/knowledge/)…
Develop an external-service integration design as a DESIGN SEED in .aid/design/integration.md -- the external service, the client/adapter surface, and the auth and failure modes. Use this skill when how to talk to an external service is still being worked out, including how failures should behave. Grounded in the…
Develop a scheduled or background job design as a DESIGN SEED in .aid/design/job.md -- the trigger, the work it performs, and its idempotency and failure handling. Use this skill when a job's schedule, its work, and its retry behaviour are still being decided. Grounded in the Knowledge Base (.aid/knowledge/) and the…
Develop a messaging design as a DESIGN SEED in .aid/design/messaging.md -- the message/event schema, its channel, and its emission points. Use this skill when an event's schema and who consumes it are still being worked out. Grounded in the Knowledge Base (.aid/knowledge/) and the project source. It WRITES NO…
Draw the MVP line as a DESIGN SEED in .aid/design/mvp.md -- what is in the first shippable slice, what defers, and the reason for each cut. Use this skill when what the first shippable slice should contain is still an open question. Grounded in the Knowledge Base (.aid/knowledge/) and the project source. It WRITES NO…
Develop the project's committed direction as a DESIGN SEED in .aid/design/roadmap.md -- what is committed vs. merely wanted, the sequencing rationale, and the alternatives being rejected and why. Use this skill when the direction for the coming horizons is still being argued out, and you want it settled as a seed…
Develop the technology choice as a DESIGN SEED in .aid/design/stack.md -- languages, runtimes, frameworks, and build and test tooling with versions, plus the alternatives rejected and why. Use this skill when which technologies to build on is still an open choice. Grounded in the Knowledge Base (.aid/knowledge/) and…
★not rated 5 yesterdayA170 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: