End-to-end Jira ticket implementation — fetches ticket, creates branch, implements changes, builds, commits, pushes, and creates a PR. Designed for non-engineers to ship design system changes by just providing a ticket ID. Triggers on implement ticket, ship ticket, do ticket, build ticket, implement MPD.
The English summary is being prepared. Showing the original description.
mParticle/aquarium☆ 8Updated Oct 14, 2026
Guides feature development and bug fixes by writing tests before implementation. It confirms each test fails for the expected reason, adds only enough code to pass, and checks the full test suite before completion.
- Implementing a new feature from tests
- Reproducing a bug in a test before fixing it
- Refactoring while keeping tests passing
obra/superpowers☆ 302.2KUpdated Oct 10, 2026
Turn a specification and its tickets into code by coordinating multiple agents around task dependencies. Combine their work on one integration branch, use test-driven development, review the result, and close tickets through the issue tracker’s workflow.
- Implementing a specification with multiple tickets
- Working on independent tickets in parallel
- Combining implementations on one integration branch
mattpocock/skills☆ 297.7KUpdated Oct 20, 2026
Organize feature development using files in the repository. Break larger goals into user stories, assign them to sprints, guide implementation and review, and track progress through confirmed merges without an external project management tool.
- Plan feature delivery without an external project management tool
- Break requirements into implementable user stories
- Choose stories for the next sprint
affaan-m/ECC☆ 284.3KUpdated Oct 20, 2026
Map the impact of a proposed change using real dependencies and project documentation. Identify affected code, data, interfaces, tests, and release steps, then compare the implemented changes with the plan to expose gaps and unverified risks.
- Map callers and tests affected by an API change
- Review database migration and recovery plans
- Check authentication changes across modules
affaan-m/ECC☆ 284.3KUpdated Oct 20, 2026
Coordinate a new feature from research and planning through tests, implementation, review, and commit. Assign phases to matching ECC agents, write failing tests before implementation, and pause for approval of the plan and before committing.
- Adding a capability that does not exist yet
- Implementing a feature with tests written first
- Reviewing an authentication feature for security
affaan-m/ECC☆ 284.3KUpdated Oct 20, 2026
Turn clear requirements into small implementation tasks with acceptance criteria, verification steps, dependencies, and estimated scope. Produce a written plan and ordered task list, with checkpoints and opportunities for parallel work identified before coding begins.
- Breaking a large feature into implementable tasks
- Ordering work by dependencies
- Defining completion criteria and verification steps
addyosmani/agent-skills☆ 108.7KUpdated Oct 14, 2026
Implement larger changes as small, working pieces. Each piece goes through testing, verification, and a focused commit, with guidance on choosing boundaries, hiding unfinished features behind switches, and keeping changes easy to roll back.
- Building a feature across multiple files
- Implementing the next task from a plan
- Merging unfinished features behind a feature flag
addyosmani/agent-skills☆ 108.7KUpdated Oct 14, 2026
Turn Figma designs into production-ready frontend code that closely matches the original visuals. Use it to hand design frames directly to a frontend agent and guide implementation toward a faithful reproduction of the design.
- Implementing a screen from a Figma design
- Handing Figma frames to a frontend agent
- Reproducing a design's appearance in code
nexu-io/open-design☆ 102.6KUpdated Oct 20, 2026
Implement animated effects, transitions, and movement in Flutter apps. Use it when adding motion to native iOS and Android app interfaces, with support for turning requests for animation into implementation work.
- Adding animated effects to a Flutter app
- Implementing animated screen transitions
- Adding motion to iOS and Android app interfaces
nexu-io/open-design☆ 102.6KUpdated Oct 20, 2026
Create a phased implementation plan for a feature or complex development task. It investigates documentation and existing examples, identifies supported APIs, and records concrete tasks, references, and verification checks for each phase.
- Planning a feature before implementation
- Checking documented APIs before choosing an approach
- Splitting development work across separate chat sessions
thedotmack/claude-mem☆ 101.8KUpdated Oct 20, 2026
Carry out a phased implementation plan with subagents assigned to implementation, verification, pattern checks, and code review. Each phase must pass verification before changes are committed and pushed, with context prepared for the next phase.
- Execute a plan created with make-plan
- Delegate implementation work by phase
- Verify changes and review code before committing
thedotmack/claude-mem☆ 101.8KUpdated Oct 20, 2026
Turn an approved specification into pseudocode, a plain outline of program logic, and an architecture defining module responsibilities and API inputs and outputs. After user confirmation, proceed with implementation and unit tests based on those designs.
- Turning an approved specification into pseudocode
- Defining module boundaries and dependency rules
- Designing API inputs, outputs, and error responses
ruvnet/ruflo☆ 77.3KUpdated Oct 19, 2026
Compare an implementation with its OpenSpec specifications, tasks, and design decisions before archiving the change. Get a report on completion, requirement coverage, and consistency, with prioritized issues, actionable recommendations, and explicit limits where evidence is missing.
- Check for unfinished tasks before archiving a change
- Find gaps between specifications and implementation
- Review scenario tests and adherence to design decisions
Fission-AI/OpenSpec☆ 72.5KUpdated Oct 19, 2026
Research existing code, documents, and relevant sources before producing a practical plan for implementation, migration, debugging, or evaluation. The plan explains key decisions, ordered steps, and validation checks, giving users something concrete to review before execution.
- Plan implementation steps before changing code
- Design a phased migration with rollback steps
- Break work into separate commits or pull requests
asgeirtj/system_prompts_leaks☆ 69.9KUpdated Oct 16, 2026
Implement approved development stories and code changes with Amelia, a senior software engineer persona. Follow a test-first process: write a failing test, make it pass, then improve the code while checking every acceptance criterion.
- Implementing an approved development story
- Making code changes with a test-first process
- Checking implementation against acceptance criteria
bmad-code-org/BMAD-METHOD☆ 54.3KUpdated Oct 19, 2026
Implement or review login and access controls for applications and APIs. Helps define token lifetimes, session handling, and permissions for specific resources, with checks for user identity, organization boundaries, credential storage, and authentication failures.
- Implement login and session management
- Review access controls for REST or GraphQL APIs
- Design social login or single sign-on
sickn33/agentic-awesome-skills☆ 48KUpdated Oct 19, 2026
Manage coding work from issue intake through implementation, review, deployment, and acceptance checks. Track each completion requirement against fresh evidence, with defined retry limits and explicit escalation when progress needs human input.
- Taking a ready issue through implementation and verification
- Coordinating implementation, review, and deployment handoffs
- Checking runtime behavior against acceptance criteria
sickn33/agentic-awesome-skills☆ 48KUpdated Oct 19, 2026
Assess a new or existing AI project by examining its code, goals, and constraints. Recommend skills confirmed to exist in the available registry, then outline tasks and implementation phases with dependencies, completion criteria, and checks.
- Planning the first steps of a new AI project
- Assessing technical issues in an existing project
- Selecting relevant skills from an available registry
sickn33/agentic-awesome-skills☆ 48KUpdated Oct 19, 2026
Coordinate a development task from planning through implementation and review. Choose whether to proceed after seeing the plan, then receive a report covering commits, verification results, review findings, and any work left unfinished.
- Plan, implement, and review a feature
- Review a plan before authorizing implementation
- Start implementation from an existing plan
abhigyanpatwari/GitNexus☆ 48KUpdated Oct 19, 2026
Guides contributors through adding a new programming language to Airflow, covering SDK structure, runtime coordination, communication rules, executable packaging, tests, and the documentation and configuration changes needed for a pull request.
- Adding support for a new programming language
- Choosing how Airflow launches a language runtime
- Implementing communication and executable bundles
apache/airflow☆ 47.2KUpdated Oct 19, 2026
Design and implement interface responses such as button feedback, loading indicators, page transitions, and swipe gestures. Use motion to communicate actions and state changes, with guidance on timing, performance, and support for people who prefer reduced animation.
- Adding hover and click feedback to buttons
- Showing loading placeholders and progress indicators
- Creating transitions for pages and interface components
wshobson/agents☆ 41.2KUpdated Oct 20, 2026
Plan and implement user login and access permissions using sessions, JWT tokens, or OAuth2. Apply role-based permissions, protect APIs, and review common weaknesses in password handling, cookies, token expiration, and server-side checks.
- Implementing user login and logout
- Adding social login or enterprise SSO
- Controlling access by user role
wshobson/agents☆ 41.2KUpdated Oct 20, 2026
Review and write Solidity smart contracts with security in mind. Address reentrancy, where external calls trigger repeated execution, along with numeric overflow and access control issues, using implementation patterns, security tests, and documentation for audit preparation.
- Review existing smart contracts for vulnerabilities
- Implement withdrawal logic that resists reentrancy
- Test overflow protection and access restrictions
wshobson/agents☆ 41.2KUpdated Oct 20, 2026