v2026.11.3 — Plan Milestone Work and Review Host Exposure
Milestone issue delivery with a dry-run preview, read-only host exposure and hardening reviews, Factory hook guidance, and scope-focused planning templates.
AIWG 2026.11.3 - Plan milestone work and review host exposure
AIWG 2026.11.3 helps your assistant work through a milestone with clear tasks and checks. It also adds read-only reviews of host exposure and hardening, explains Factory hook prerequisites, and updates planning templates to focus on scope and acceptance.
Preview a milestone before handing out work
The address-issues skill now has a milestone mode. It reviews the open issues, identifies work that is ready or blocked, and gives workers bounded tasks with clear acceptance checks. Changes receive independent verification before delivery, and the workflow follows your repository's rules for merging, closing issues and checking CI after a merge.
Start by asking your assistant:
Use address-issues to work through milestone “settings-page” with workers. Show me the dry-run plan first.
The preview shows the proposed tasks and their destinations without launching workers, changing files or updating the tracker. Review blocked or unclear issues before starting the work. The skill arguments are `--milestone settings-page --dispatch workers --dry-run`; your assistant loads the skill and uses them. See Find One Capability for the discovery flow.
Understand which services may be exposed
New exposure-analysis and host-hardening skills help review the services a host makes available. They compare listening ports, Docker port publishing and firewall captures, then report findings and recommendations. A Docker port without an explicit bind address is one example they flag for review.
Ask your assistant to find the exposure-analysis skill for a firewall review, or host-hardening for a hardening assessment. Name the host and the read-only collection you authorize, or supply sanitized captures. These skills leave rules, containers and services unchanged. Missing or unsupported evidence stays marked unknown, so an incomplete capture does not become a claim that a port is closed.
Get clearer guidance for Factory hooks
Factory/droid loads project hooks only when the folder is trusted and the project is a git repository with at least one commit. Deployment and doctor now explain which prerequisite is missing. Open the project in droid to review folder trust, and create the initial commit yourself when needed.
Interactive droid sessions can use prompt discovery once those prerequisites are met. Non-interactive `droid exec` still relies on startup instructions because it has no prompt hooks. The hook guide explains the setup.
Describe the work and its acceptance checks
More planning and report templates now ask for scope, roles, prerequisites and acceptance checks in place of estimated durations or effort. This covers planning cards, investigation plans, regression and research gap reports, and media-marketing-kit templates. Use the updated template when starting the next document; fields for observed dates and commitments you have made remain.
If you are upgrading
- After updating, ask your assistant to refresh AIWG to receive the updated skills and templates.
- In Factory/droid, review folder trust and confirm the repository has a commit if project hooks are inactive.
- Claude workers now accept CLI versions from 2.1.295 up to, but excluding, 2.2.0, including 2.1.319.
See the CHANGELOG entry for the complete release record dated November 8, 2026.