Total Skills
7
Author Profile: wamalalawrence
Skills published by wamalalawrence with real stars/downloads and source-aware metadata.
Total Stars
0
Total Downloads
0
Skills Performance
Comparison chart based on real stars and downloads signals from source data.
delivery-planner
0
Stars
0
Downloads
0
manual-tester
0
Stars
0
Downloads
0
product-owner
0
Stars
0
Downloads
0
software-engineer
0
Stars
0
Downloads
0
code-reviewer
0
Stars
0
Downloads
0
issue-investigator
0
Stars
0
Downloads
0
test-automation-engineer
0
Stars
0
Downloads
0
Published Skills
delivery-planner
Phased delivery planning workflow that turns a single large or multi-day task (feature, refactor, migration, multi-step investigation, multi-PR bug fix) into two persistent artifacts: a concise destination brief and a sequence of small, self-contained execution phases. Use when: a task is too large to fit one agent's working context, when work will span multiple sessions or multiple agents, or when the user wants a written plan before any implementation, refinement, investigation, or test design begins. Each phase is sized so a fresh agent loaded with the destination plus that one phase has enough — and only enough — context to execute it well. Hands phases off to software-engineer, issue-investigator, product-owner, manual-tester, or test-automation-engineer; never re-invokes them itself.
Repository SourceNeeds Review
manual-tester
Manual testing workflow for validating intended behavior, exploring workflows, finding defects, documenting actual vs expected behavior, collecting evidence, and preparing retest guidance. Use when: planning or executing manual tests, validating acceptance criteria, doing exploratory testing, checking edge cases, reporting defects, or identifying regression and automation candidates. Collaborates with product-owner for intended behavior, software-engineer for technical risk areas, and test-automation-engineer for high-value automation candidates.
Repository SourceNeeds Review
product-owner
Product ownership workflow for turning product goals, stakeholder needs, Jira tickets, and rough ideas into clear, testable, implementation-ready work. Use when: clarifying goals, refining requirements, defining scope, writing acceptance criteria, preparing Jira-ready stories or tasks, or handing work to engineering and testing. Collaborates with software-engineer for feasibility and tradeoffs, manual-tester for scenario coverage, and test-automation-engineer for automation-friendly acceptance criteria.
Repository SourceNeeds Review
software-engineer
Senior-level pair-programming workflow for software engineering work. Use when: making code changes, bug fixes, refactors, feature implementation, issue-description driven fixes, code review, PR preparation, migration scripts, API changes, or security review. Connects implementation, review, and issue resolution in one context-aware loop. Uses compact project and issue context first, then expands only when risk or ambiguity requires it. Invokes the nested code-reviewer skill at the end of Implementation and again at the end of QA, and auto-iterates the engineer↔reviewer pair-programming loop (address findings, re-invoke reviewer, repeat until convergence or `${CODE_REVIEWER_MAX_ROUNDS}`) instead of bouncing each round back to the user. Reuses issue-investigator when issue context, root cause, or expected behavior needs deeper evidence.
Repository SourceNeeds Review
code-reviewer
Issue-aware code review workflow for working diffs, commits, branches, and pull requests. Use when: reviewing implementation against a Jira ticket, GitHub issue, bug report, feature request, task description, acceptance criteria, or general engineering quality bar. Applies two layers: issue/ticket alignment first, then general engineering quality. Reuses issue-investigator when expected behavior, root cause, or issue context is unclear, and reuses software-engineer for architecture, implementation quality, testability, and production-risk judgment.
Repository SourceNeeds Review
issue-investigator
Issue investigation workflow for Jira tickets, GitHub issues, support tickets, incidents, regressions, feature requests, and technical tasks. Use when: understanding expected vs actual behavior, classifying issue type, gathering evidence, reproducing problems, analyzing root cause, refining tickets before implementation, or recommending the next action. Reuses software-engineer for technical code analysis and implementation feasibility, and supports code-reviewer by producing reliable issue context before review.
Repository SourceNeeds Review
test-automation-engineer
Test automation engineering workflow for choosing the right test level, designing maintainable automated checks, preventing flakiness, integrating tests into CI, and deciding when not to automate. Use when: creating or reviewing automated regression tests, API tests, contract tests, integration tests, UI/e2e tests, fixtures, selectors, or test reporting. Collaborates with software-engineer for code quality and architecture, manual-tester for real scenarios and defects, and product-owner for acceptance criteria and business-critical workflows.
Repository SourceNeeds Review