# Appforge Manager Issue Management > Manage Appforge issues at the manager-agent level. Use when triaging agent:remote issues, finding Ready work to start, resuming In Progress work, checking dependency relationships, or coordinating project board status via appforge-mcp. Use when this capability is needed. - Skill: `tomevault-io/appforge-manager-issue-management` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add tomevault-io/appforge-manager-issue-management` - Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/appforge-manager-issue-management/raw - Safety review: pending (external: skill-scanner PASS, skillspector PASS) - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: AI & ML - Author: tomevault-io (https://skillmd.com/u/tomevault-io) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/tomevault-io/appforge-manager-issue-management --- # Appforge Manager Agent Issue Management ## Overview Identify which remote-agent issues should start or resume based on status, labels, and dependency relationships. ## Workflow 1. Find issues that should start: - Project status: `Ready` (use appforge-mcp for project board status). - Label: `agent:remote`. - No blocking issues in relationships that are not `Done`. 2. Find issues that should resume: - Project status: `In Progress` (use appforge-mcp). - Label: `agent:remote`. - Not currently claimed by another agent. 3. When evaluating dependencies: - Use GitHub issue relationships to confirm blockers. - If blockers are not `Done`, do not start the issue. 4. Surface the final list to the user with the reasoning (status, label, and blockers). ## Notes - Use `github-mcp` for issue lookups, labels, assignees, and relationships. - Use `appforge-mcp` for project board status reads/updates. - If a request includes changing issue status or assignment, confirm before acting. --- > Converted and distributed by [TomeVault](https://tomevault.io/claim/day-in-the-country-llc) — claim your Tome and manage your conversions.