We let agents run the boring half of our projects. They ask better questions than we did

Description and use

The team leveraged Claude Code skills to automate requirement clarification, ticket creation, and PR generation, reducing errors and speeding releases.

Problem

Developers often face vague tickets that lead to incomplete or incorrect code, causing delays and quality issues.

Outcome

The workflow reduced specification gaps, improved ticket quality, and automated repetitive tasks, leading to faster, higher‑quality releases.

Workflow

• Run /breakdown on a project to sync specs and detect changes.
• Use /jira <ticket-id> to interview and refine the ticket with /feature.
• Agent builds, reviews, and loops until approval.
• Create PR with /create-pr and merge.
• Run /standup the next morning to reconcile state.

Evidence

The first skill was /feature. It asks you relentlessly about open decisions or conflicts related to the feature you want to build.

Source

After using that for a while I wanted a more hands‑off approach. That became /jira.

Source

The last skill is /standup. It pulls my open PRs and review requests, my Jira issues that are not done, the local worktrees and the project folders, and reconciles them.

Source