home/coding/implement-from-pbi-prompt

Implement From PBI.prompt

GPTClaudeDeepSeek··1,135 copies·updated 2026-07-14
implement-from-pbi-prompt.prompt
---
agent: agent
description: Implement a feature end-to-end from an Azure DevOps PBI — analyze, plan, code, test, review.
tools: ['vscode', 'execute', 'read', 'agent', 'edit', 'search', 'web', 'ado/advsec_get_alert_details', 'ado/advsec_get_alerts', 'ado/core_get_identity_ids', 'ado/core_list_project_teams', 'ado/core_list_projects', 'ado/pipelines_get_build_definition_revisions', 'ado/pipelines_get_build_definitions', 'ado/pipelines_get_build_log', 'ado/pipelines_get_build_log_by_id', 'ado/pipelines_get_build_status', 'ado/pipelines_get_builds', 'ado/pipelines_get_run', 'ado/pipelines_list_runs', 'ado/pipelines_run_pipeline', 'ado/pipelines_update_build_stage', 'ado/repo_create_pull_request', 'ado/repo_create_pull_request_thread', 'ado/repo_get_branch_by_name', 'ado/repo_get_pull_request_by_id', 'ado/repo_get_repo_by_name_or_id', 'ado/repo_list_branches_by_repo', 'ado/repo_list_my_branches_by_repo', 'ado/repo_list_pull_request_thread_comments', 'ado/repo_list_pull_request_threads', 'ado/repo_list_pull_requests_by_commits', 'ado/repo_list_pull_requests_by_repo_or_project', 'ado/repo_list_repos_by_project', 'ado/repo_reply_to_comment', 'ado/repo_search_commits', 'ado/repo_update_pull_request', 'ado/repo_update_pull_request_reviewers', 'ado/repo_update_pull_request_thread', 'ado/search_code', 'ado/search_wiki', 'ado/search_workitem', 'ado/testplan_add_test_cases_to_suite', 'ado/testplan_create_test_case', 'ado/testplan_create_test_plan', 'ado/testplan_create_test_suite', 'ado/testplan_list_test_cases', 'ado/testplan_list_test_plans', 'ado/testplan_list_test_suites', 'ado/testplan_show_test_results_from_build_id', 'ado/testplan_update_test_case_steps', 'ado/wiki_create_or_update_page', 'ado/wiki_get_page', 'ado/wiki_get_page_content', 'ado/wiki_get_wiki', 'ado/wiki_list_pages', 'ado/wiki_list_wikis', 'ado/wit_add_artifact_link', 'ado/wit_add_child_work_items', 'ado/wit_add_work_item_comment', 'ado/wit_create_work_item', 'ado/wit_get_query', 'ado/wit_get_query_results_by_id', 'ado/wit_get_work_item', 'ado/wit_get_work_item_type', 'ado/wit_get_work_items_batch_by_ids', 'ado/wit_get_work_items_for_iteration', 'ado/wit_link_work_item_to_pull_request', 'ado/wit_list_backlog_work_items', 'ado/wit_list_backlogs', 'ado/wit_list_work_item_comments', 'ado/wit_list_work_item_revisions', 'ado/wit_my_work_items', 'ado/wit_update_work_item', 'ado/wit_update_work_items_batch', 'ado/wit_work_item_unlink', 'ado/wit_work_items_link', 'ado/work_assign_iterations', 'ado/work_create_iterations', 'ado/work_get_iteration_capacities', 'ado/work_get_team_capacity', 'ado/work_list_iterations', 'ado/work_list_team_iterations', 'ado/work_update_team_capacity', 'memory/*', 'sequential-thinking/*', 'azure-mcp/search', 'todo']
---

# Implement from PBI

Implement a feature end-to-end from an Azure DevOps PBI. Follow the persona, conventions, and delegation rules defined in `AGENTS.md`. Apply `general.instructions.md` and `tests.instructions.md` throughout. Use the `C# Expert` agent for .NET implementation decisions.

Work autonomously, accurately, and incrementally — one compilable step at a time.

---

## Phase 0: Identify the PBI

If the user provided a PBI ID (a number), use it directly. If not, ask:

> What is the PBI ID (Azure DevOps Work Item ID) to implement?

Do NOT proceed until you have a valid numeric Work Item ID.

---

## Phase 1: Deep PBI Analysis

Use Azure DevOps MCP tools to gather the full picture. Execute these steps in order:

1. **Fetch the PBI** — retrieve the work item by ID (project: `<!-- TODO: Replace with your ADO project name -->`). Extract: title, description, acceptance criteria, state, assigned to, iteration, area path.
2. **Fetch the Parent** — if the PBI has a parent link, retrieve it. Understand the epic/feature context and any overarching requirements or constraints.
3. **Fetch all Children** — if the PBI has child work items (tasks, sub-items), retrieve each one. Map out the full scope of work including task breakdown, estimates, and any already-completed tasks.
4. **Fetch linked items** — check for related work items, predecessor/successor links, or referenced PRs that provide additional context.

Compile a structured summary:

when to use it

Community prompt sourced from the open-source GitHub repo AndreasKarz/Vibe-Coding-Dev-Setup (NOASSERTION). A "Implement From PBI.prompt" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.

tags

codingcommunitydeveloper

source

AndreasKarz/Vibe-Coding-Dev-Setup · NOASSERTION