Menu
Multi-step pipeline that takes a ticket from research to PR — research → spec → code → review + test → PR. Use for any ticket in agent-hub/tickets/.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Python coding conventions for this workspace. Use when writing or reviewing Python in taskflow-api or scan-simulator — apply automatically, without asking for confirmation.
Use when suggesting a commit message, branching, staging, committing, merging, resolving conflicts, or pushing in any project of this workspace.
Draft well-structured Pull Request titles and descriptions. Use whenever the user wants to open a PR, write a pull request, draft a PR description, or prepare a PR for review — also when they give a ticket ID or branch name alongside code changes without saying "pull request".
Draft a release note from recent commits/closed tickets. Used in Part 2 of the session as the "simple skill" example.
Answer "what code implements this?" from a ticket, spec, or plain question — returns the registered call chain from the flow registry plus the impact of changing it.
| name | implement-feature |
| description | Multi-step pipeline that takes a ticket from research to PR — research → spec → code → review + test → PR. Use for any ticket in agent-hub/tickets/. |
Run the stages in order. Do not skip; do not merge stages.
agent-hub/flow-registry/ to find the implementing code and impacted flows.agent-hub/knowledge-base/ for proven patterns touching the same area.feature/<ticket-id>-<slug>. Follow the project AGENTS.md conventions.<ticket-id>: <imperative summary>.