ai4pb-wrapup

Extract Verified tasks and issues into the knowledge graph during sprint wrap-up.

Updated Mar 1, 2026
One-click install
npx skills add https://github.com/derekhu0002/ai4pb-orchestrator --skill ai4pb-wrapup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ai4pb-wrapup
Source: https://github.com/derekhu0002/ai4pb-orchestrator/tree/main/.opencode/skills/ai4pb-wrapup
Command: npx skills add https://github.com/derekhu0002/ai4pb-orchestrator --skill ai4pb-wrapup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates sprint wrap-up by extracting only Verified tasks and issues from design task sources and consolidating evidence into the knowledge graph.

Core Features & Use Cases

  • Task Status Sync (Session Delta): Re-scan design/tasks/taskandissues_for_LLM.md at wrap-up time and extract only ToDos and Issues entries whose Status is Verified.
  • KG View Resolution Rules: Resolve View references globally by loading design elements, relationships, and views, then reverse-lookup IDs and verify content against the top-level KG.
  • Quick Path & Validation: Follow primary source tasks first, with a fallback to the KG SystemArchitecture.json when markdown is missing, while enforcing Verified-only filtering and ignoring empty placeholders.

Quick Start

Run the wrap-up session to extract Verified tasks and verify views from the knowledge graph.

Frequently Asked Questions about ai4pb-wrapup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate sprint wrap-up to extract only verified tasks?

Automate sprint wrap-up by re-scanning design task sources to extract only tasks and issues with a Verified status, consolidating evidence directly into the knowledge graph. Verified-only filtering ensures traceability for architecture-driven SCRUM workflows.

What is the knowledge graph view resolution process for architecture tasks?

Knowledge graph view resolution loads design elements, relationships, and views globally, then reverse-lookup IDs to verify content against the top-level knowledge graph. This cross-referencing maintains consistency across architecture tasks at iteration end.

How do I sync verified task statuses to the knowledge graph at iteration end?

Sync task statuses by re-scanning the taskandissues markdown file at wrap-up time to extract only Verified ToDos and Issues. It applies a deterministic fast-path for loading tasks and validates content against the top-level knowledge graph.

Can I use the knowledge graph JSON fallback when task markdown is missing?

Yes, you can use SystemArchitecture.json as a fallback when task markdown is missing. The quick path validation follows primary source tasks first, falling back to the knowledge graph while enforcing Verified-only filtering and ignoring empty placeholders.

Does this sprint wrap-up tool work without external dependencies?

Yes, this sprint wrap-up tool works without external dependencies. It directly re-scans local markdown task sources and validates knowledge graph views natively, extracting only Verified tasks to ensure architecture-driven SCRUM consistency.