---

name: sdlc description: "MUST BE LOADED for any coding task: implementing features, fixing bugs, writing code, refactoring, or making changes. This skill provides the mandatory step-by-step workflow for orchestrating the complete software development lifecycle using specialized agents. Load this skill when the user asks to 'add', 'create', 'build', 'fix', 'update', 'change', 'implement', or 'refactor' anything."

SDLC Workflow Skill

This skill defines the mandatory workflow for all coding tasks. Follow these steps IN ORDER. Skipping steps is FORBIDDEN.

CRITICAL RULES

YOU MUST USE THE TASK TOOL TO DELEGATE ALL WORK TO SPECIALIZED AGENTS.

• ❌ NEVER write code yourself
• ❌ NEVER create files yourself
• ❌ NEVER make commits yourself
• ❌ NEVER skip steps
• ❌ NEVER skip tests (test.skip, it.skip, describe.skip are FORBIDDEN)
• ✅ ALWAYS use Task tool with the specified subagent_type
• ✅ ALWAYS verify each step before proceeding
• ✅ ALWAYS fix, replace, refactor, or remove tests - never skip them

FAILURE TO USE AGENTS = WORKFLOW FAILURE

Test Policy

⛔ NEVER skip tests. If a test cannot pass:

• Fix it - Update assertions to match correct behavior
• Replace it - Write a new test that properly validates the behavior
• Refactor it - Restructure to test what's actually testable
• Remove it - Delete entirely if it tests something that no longer exists

If tests require infrastructure (auth, database, external services), SET UP that infrastructure. Do not skip tests because setup is hard.

---

MANDATORY STEPS (Execute in Order)

STEP 0: GitHub Authentication

Execute FIRST before anything else.

gh auth status

If fails: STOP. Tell user to run gh auth login. Do NOT proceed.

---

STEP 1: Workspace Preparation

Create clean feature branch BEFORE any implementation.

1.1 Check for uncommitted changes

git status

If uncommitted changes exist:

• Ask user: "Uncommitted changes found. Stash them or abort?"
• If stash: git stash push -m "SDLC auto-stash"
• If abort: STOP

1.2 Sync and create branch

git fetch origin
git checkout main
git pull origin main
git checkout -b <type>/<short-description>

Branch types: feat, fix, refactor, docs, test, chore

⛔ DO NOT PROCEED until branch is created

---

STEP 2: Requirements Analysis

MANDATORY: Launch requirements-analyzer agent.

Task tool:
  subagent_type: "fx-dev:requirements-analyzer"
  prompt: "Analyze requirements for: [TASK DESCRIPTION]

           - Analyze task/issue/error to understand requirements
           - Use WebSearch to research technologies
           - Use WebFetch for referenced URLs
           - Use AskUserQuestion for ambiguities
           - Analyze codebase for patterns

           Output: Complete requirements with acceptance criteria"
  description: "Analyze requirements"

For GitHub issues, fetch first:

gh issue view [NUMBER] --json title,body,labels,comments

⛔ DO NOT PROCEED until requirements are complete

---

STEP 3: Planning

MANDATORY: Launch planner agent.

Task tool:
  subagent_type: "fx-dev:planner"
  prompt: "Create implementation plan for:

           [REQUIREMENTS FROM STEP 2]

           - Break into atomic steps
           - Identify files to modify
           - Determine test requirements
           - Flag if multiple PRs needed

           Output: Numbered implementation steps"
  description: "Plan implementation"

For GitHub issues, also update issue:

Task tool:
  subagent_type: "fx-dev:issue-updater"
  prompt: "Update issue #[NUMBER] with plan. Add label: in-progress"
  description: "Update issue"

⛔ DO NOT PROCEED until plan exists

---

STEP 4: Implementation

MANDATORY: Launch coder agent.

Task tool:
  subagent_type: "fx-dev:coder"
  prompt: "Implement this plan:

           [PLAN FROM STEP 3]

           Requirements:
           - Atomic commits (format: type(scope): message)
           - Follow existing patterns
           - Run tests
           - Do NOT create PR"
  description: "Implement changes"

Verify commits exist:

git log --oneline -5
git diff main --stat

⛔ DO NOT PROCEED until commits exist on feature branch

---

STEP 5: Pull Request Creation (as Draft)

MANDATORY: Launch pr-preparer agent. ALL PRs MUST be created as drafts.

Task tool:
  subagent_type: "fx-dev:pr-preparer"
  prompt: "Create DRAFT PR for current branch.
           Task: [ORIGINAL TASK]
           Summary: [WHAT WAS IMPLEMENTED]

           CRITICAL: Use --draft flag. Never create non-draft PRs.
           - Push branch if needed
           - Create PR with: gh pr create --draft
           - Reference related issues
           - Return PR number and URL
           - Tell user to run 'gh pr ready <NUMBER>' when ready"
  description: "Create draft PR"

Capture the PR number for remaining steps.

⛔ DO NOT PROCEED until PR is created

---

STEP 6: Review & Quality

MANDATORY: Execute ALL sub-steps.

6.1 Self-Review

Task tool:
  subagent_type: "fx-dev:pr-reviewer"
  prompt: "Review PR #[NUMBER] for:
           - Code quality
           - Test coverage
           - Security issues
           - Performance

           Output: Issues found (if any)"
  description: "Review PR"

6.2 Fix Issues (if any found)

Task tool:
  subagent_type: "fx-dev:coder"
  prompt: "Fix these issues in PR #[NUMBER]:
           [ISSUES FROM REVIEW]"
  description: "Fix review issues"

6.3 Request and Wait for Copilot Review (10 minute timeout)

First, request Copilot review via the GitHub API:

# Request Copilot review using JSON body format (most reliable)
gh api --method POST /repos/{owner}/{repo}/pulls/[PR_NUMBER]/requested_reviewers \
  --input - <<'EOF'
{"reviewers":["copilot-pull-request-reviewer[bot]"]}
EOF

Then use the bundled script to poll for completion (10 minute timeout):

# IMPORTANT: Use the FULL path from the skill's base directory
bash [SKILL_BASE_DIR]/skills/sdlc/scripts/wait-for-copilot-review.sh [PR_NUMBER]

⚠️ CRITICAL: You MUST wait the full 10 minutes. Do NOT fall back to manual polling with shorter waits. If the script exits with code 2 (review not detected as requested), re-request the review using the JSON body format above and run the script again.

Script behavior:

• Checks if Copilot review was requested
• Polls every 60s until review is received (timeout: 600s / 10 minutes)
• Exit 0: Review received -> proceed to Step 6.4 immediately
• Exit 1: Timeout after 10 minutes -> proceed to Step 6.4 anyway (will find no threads)
• Exit 2: Review request not detected -> re-request using JSON body format above, then re-run script

6.4 Handle Automated Review Feedback (Copilot/CodeRabbit)

ALWAYS invoke this skill after Step 6.3, regardless of whether the Copilot review arrived or timed out. This skill detects and resolves all unresolved automated review threads.

Skill tool: skill="fx-dev:resolve-pr-feedback"

⛔ DO NOT PROCEED until all review issues resolved

---

STEP 7: CI/CD Monitoring

MANDATORY: Execute ALL sub-steps. Maximum 3 fix iterations.

7.1 Analyze Workflow Configuration

Examine .github/workflows/ to determine if CI checks trigger on draft PRs:

# Read all workflow files and check their trigger configuration
ls .github/workflows/

Look for pull_request event triggers in each workflow file:

• Triggers on drafts: pull_request: with no types: filter, or types: includes opened / synchronize without special draft exclusion
• Does NOT trigger on drafts: Workflow uses pull_request_target, or has conditional like if: github.event.pull_request.draft == false, or no pull_request trigger at all

Output: Whether CI checks will run on a draft PR.

7.2 Ensure CI Checks Are Triggered

If workflows do NOT trigger on draft PRs:

gh pr ready [PR_NUMBER]

This marks the PR as ready for review, which triggers CI workflows that only run on non-draft PRs.

If workflows DO trigger on drafts: No action needed — checks should already be running or queued.

7.3 Wait for CI Checks to Start and Complete

Run the bundled CI check script in the background, then poll its output every 60 seconds:

# Step 1: Launch the script in the background using Bash tool with run_in_background=true
bash [SKILL_BASE_DIR]/skills/sdlc/scripts/wait-for-ci-checks.sh [PR_NUMBER]

⚠️ CRITICAL: Use run_in_background: true on the Bash tool call. Then poll the background task output every 60 seconds using TaskOutput with block: false to check progress. This lets you report status updates to the user while waiting.

Polling loop:

1. Launch script with run_in_background: true
2. Every 60 seconds: check task output with TaskOutput(task_id, block: false, timeout: 5000)
3. Report progress to user (e.g., "CI checks: 2 pending, 3 completed")
4. When the task completes, read the final output to determine the exit code and results
5. Do NOT just set a 15-minute timeout and block — you must actively poll and report progress

⛔ NEVER use a blocking Bash call with a long timeout for this script. Always use background execution + polling.

Script behavior:

• Phase 1: Waits for checks to appear (some repos have a startup delay)
• Phase 2: Polls every 30s until all checks complete (timeout: 900s / 15 minutes)
• Exit 0: All checks passed → proceed to Step 8
• Exit 1: One or more checks failed → proceed to Step 7.4
• Exit 2: Timeout waiting for checks → report to user, ask whether to continue waiting or proceed
• Exit 3: Invalid arguments or gh error

7.4 Handle CI Failures (LOOP — max 3 iterations)

If Step 7.3 exits with code 1 (failures detected):

Skill tool: skill="fx-dev:resolve-ci-failures"

Pass the failure details from the script output to the skill. The skill will:

1. Analyze failure logs and identify root causes
2. Delegate fixes to the coder agent
3. Push the fixes

After the skill completes and fixes are pushed, GO BACK TO Step 7.3 — re-run the wait script to monitor the new check run. This creates a loop:

Step 7.3 (wait) → fail → Step 7.4 (fix) → Step 7.3 (wait) → ...

⚠️ Maximum 3 iterations. Track the current iteration count. If checks still fail after 3 fix attempts, STOP and report the persistent failures to the user with full details.

⛔ DO NOT PROCEED until all checks pass or max iterations reached

---

STEP 8: Finalization

8.1 Final Verification

gh pr view [NUMBER] --json state,mergeable,reviews,statusCheckRollup

Confirm:

• PR is open and mergeable
• All checks pass
• No unresolved comments

8.2 Update Task Tracking Docs

MANDATORY: Mark completed tasks in the relevant spec or project doc.

If a spec file, project doc, or task list was referenced in the original request (e.g., a docs/specs/ file or docs/PROJECT.md), use it directly. If none was provided, search for the relevant tracking doc:

# Look for spec files or project docs that reference the work being done
grep -rl "keyword from task" docs/specs/ docs/PROJECT.md 2>/dev/null || true

Once identified, update the doc to mark completed tasks:

• Check off completed items (e.g., - [ ] → - [x])
• Only mark items that are actually addressed by the changes in this PR
• Commit the doc update to the PR branch

Task tool:
  subagent_type: "fx-dev:coder"
  prompt: "Update task tracking in [DOC_PATH]:
           - Read the doc and identify tasks completed by PR #[NUMBER]
           - Mark those tasks as done (check off checkboxes)
           - Do NOT mark tasks that were not addressed
           - Commit the change with: docs: mark completed tasks in [DOC_NAME]
           - Push to the PR branch"
  description: "Update task tracking"

If no relevant tracking doc is found, skip this step.

8.3 Update Issue (if applicable)

Task tool:
  subagent_type: "fx-dev:issue-updater"
  prompt: "Update issue #[NUMBER]: Link PR, set label ready-for-review"
  description: "Update issue"

8.4 Report to User

✅ PR #[NUMBER] ready: [URL]

Changes:
- [summary bullets]

Awaiting your approval to merge.

⚠️ NEVER MERGE WITHOUT USER APPROVAL

---

Workflow Variations

GitHub Issue URL

1. STEP 0: Auth check
2. STEP 1: Branch as fix/issue-123-description
3. Fetch issue: gh issue view [NUMBER] --json title,body,labels,comments
4. STEP 2-8: Standard (use issue-updater in Steps 3 and 8)

Quick Fix (fix:, error:, bug: prefix)

1. STEP 0: Auth check
2. STEP 1: Branch as fix/short-error-desc
3. STEP 2: Focus on error analysis, root cause
4. STEPS 3-8: Standard

Multi-PR Tasks

1. Complete STEPS 1-8 for first PR
2. STOP - Wait for user approval
3. Only after approval: Start next PR
4. Track with TodoWrite

NEVER have multiple PRs open simultaneously

---

Error Handling

Error	Action
Agent fails	Retry once with adjusted params, then STOP and report
Git conflict	STOP, report to user, wait for resolution
Tests fail	coder agent fixes, rerun until pass
Auth fails	STOP, request gh auth login

---

Agent Quick Reference

Step	Agent	subagent_type
2	Requirements Analyzer	fx-dev:requirements-analyzer
3	Planner	fx-dev:planner
3,8	Issue Updater	fx-dev:issue-updater
4,6.2	Coder	fx-dev:coder
5	PR Preparer	fx-dev:pr-preparer
6.1	PR Reviewer	fx-dev:pr-reviewer
6.4	PR Feedback Resolver	Skill: fx-dev:resolve-pr-feedback
7.4	CI Failure Resolver	Skill: fx-dev:resolve-ci-failures

---

Success Criteria

Workflow complete when ALL true:

• ✅ Feature branch created from main
• ✅ Requirements documented
• ✅ Plan created
• ✅ Code implemented with atomic commits
• ✅ PR created with description
• ✅ Self-review done, issues fixed
• ✅ Automated review feedback resolved (Copilot/CodeRabbit)
• ✅ All CI/CD checks pass
• ✅ Task tracking docs updated (completed tasks marked in relevant spec/project doc)
• ✅ User notified, awaiting merge approval