From tdd-dev-workflow
This skill should be used when the user asks about "issue lifecycle", "PR workflow", "project board", "development process", "merge strategy", "issue status", "kanban flow", "start working on issue", "pick up an issue", "create a PR", "submit a pull request", "resume work", "continue where I left off", or needs guidance on the GitHub issue-to-merge workflow. Orchestrates the full issue-to-merge lifecycle.
How this skill is triggered — by the user, by Claude, or both
Slash command
/tdd-dev-workflow:issue-workflowThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Every issue moves through four states on the project board:
Every issue moves through four states on the project board:
Todo --> In Progress --> Review --> Done
| State | Meaning |
|---|---|
| Todo | Accepted and ready for development |
| In Progress | Actively being worked on by an assigned developer |
| Review | Pull request submitted, awaiting review |
| Done | Merged and closed |
Closes #ID.Follow this sequence for every issue, from selection through merge.
origin/main.<prefix>/<issue-id>-<short-description>.git fetch origin
git checkout -b feature/42-add-user-auth origin/main
Closes #ID reference in the PR body.<type>: #<ID> <description>
Examples:
feat: #42 add JWT authentication
fix: #87 resolve date parser null error
docs: #15 update API reference for v2 endpoints
Structure every PR body with these sections:
Closes #<issue-id>
## Summary
Brief description of what this PR accomplishes and why.
- Key change 1
- Key change 2
- Key change 3
## Test Plan
- [ ] Unit tests pass
- [ ] Integration tests pass
- [ ] Edge cases covered
- [ ] Manual verification of acceptance criteria
Closes #<issue-id> to enable auto-closing on merge.| Category | Severity | Action Required |
|---|---|---|
| Critical | High | Must fix before merge |
| Important | Medium | Should fix before merge |
| Suggestion | Low | Optional improvement |
All PRs merge using squash and merge. This means:
main.main reflects the PR title and description.Closes #ID reference.main history clean and readable.main represents one complete, reviewed feature or fix.When returning to an issue after a break or context switch, follow these steps to re-orient.
git branch -a | grep <issue-id>
If a branch exists, check it out. If not, determine whether work was already started by someone else.
gh pr list --search "<issue-id>"
Look for open, closed, or draft PRs related to the issue. Read any existing review comments.
git log --oneline origin/main..<branch-name>
Understand what has already been done. Read the diff to restore context.
| Action | Command / Convention |
|---|---|
| Create branch | git checkout -b feature/ID-desc origin/main |
| PR title | <type>: #<ID> <description> |
| Auto-close issue | Closes #<ID> in PR body |
| Merge strategy | Squash and merge |
| Post-merge cleanup | Branch auto-deleted |
| Issue states | Todo > In Progress > Review > Done |
| Skill | Reason |
|---|---|
dev-conventions | Branch naming, commit format, label system, and merge strategy are defined there |
tdd-discipline | Step 4 mandates the TDD Red-Green-Refactor cycle for all implementation |
| Component | Reason |
|---|---|
Command: create-issue | Creates structured issues following the issue templates |
Command: pick-issue | Claims issues and creates branches per this workflow |
Command: develop | Orchestrates the full lifecycle defined here |
Command: submit-pr | Creates PRs following the PR conventions |
npx claudepluginhub inteligentsensingsolutions/tdd-dev-workflow --plugin tdd-dev-workflowGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.