delivery-method
/delivery-method
Coordinate analysis, debugging, features and complete documentation through grounded specifications, adversarial plans, verified commits and authorized merge. TRIGGER WHEN: the user wants to brainstorm or design a project, define specifications or implementation plans, investigate or debug, build or refactor code, produce project documentation, resume work, or finish a delivery. Route design conversations to the owned brainstorm without requiring an explicit command. DO NOT TRIGGER WHEN: diagnosing project health without implementing (use project-lifecycle:assess-method), requesting code expla
- Author
- acaprino ↗
- Repository
- alfio-claude-plugins ↗
- Licence
- MIT
- Last repository change
- 27.10.2026
Assessment and security
- Files in this package
- 25
- Scripts
- 2
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
- 2 scripts in this package. Review them before installing, as Claude may execute them.
Scripts: scripts/artifacts.py, scripts/cycle_packets.py
What it does and when to use it
Coordinate analysis, debugging, features and complete documentation through grounded specifications, adversarial plans, verified commits and authorized merge. TRIGGER WHEN: the user wants to brainstorm or design a project, define specifications or implementation plans, investigate or debug, build or refactor code, produce project documentation, resume work, or finish a delivery. Route design conversations to the owned brainstorm without requiring an explicit command. DO NOT TRIGGER WHEN: diagnosing project health without implementing (use project-lifecycle:assess-method), requesting code expla
Original author description
Coordinate analysis, debugging, features and complete documentation through grounded specifications, adversarial plans, verified commits and authorized merge. TRIGGER WHEN: the user wants to brainstorm or design a project, define specifications or implementation plans, investigate or debug, build or refactor code, produce project documentation, resume work, or finish a delivery. Route design conversations to the owned brainstorm without requiring an explicit command. DO NOT TRIGGER WHEN: diagnosing project health without implementing (use project-lifecycle:assess-method), requesting code expla
How it works
- Load map
- Run record
- Canonical methods
- Delivery and closure
SKILL.md preview
--- name: delivery-method description: > Coordinate analysis, debugging, features and complete documentation through grounded specifications, adversarial plans, verified commits and authorized merge. TRIGGER WHEN: the user wants to brainstorm or design a project, define specifications or implementation plans, investigate or debug, build or refactor code, produce project documentation, resume work, or finish a delivery. Route design conversations to the owned brainstorm without requiring an explicit command. DO NOT TRIGGER WHEN: diagnosing project health without implementing (use project-lifecycle:assess-method), requesting code explanation, or requesting one isolated specialist audit without delivery coordination. --- # Project delivery Load `work-controller:work-record` for grants/snapshots/delivery/recovery. Own design-to-delivery; compose methods, never competing workflows. ## Load map Load by step: - First use: `references/first-use.md`. - Initialization/ADR/FRD bootstrap: `references/init.md`; `project-delivery:project-bootstrap`. - Change overview: `references/change.md`. - Preflight: `references/preflight.md`, `references/context-cycle.md`. - Interview/specification: `references/interview.md`. - Plan/execution: `references/waves.md`; dispatch: `references/worker-brief.md`. - Specifications/approval/handoff: `references/specification.md`. - Brainstorm: `references/brainstorm.md`. - Investigation: `references/investigate.md`. - Documentation: `references/document.md`. - Repair/refactor: `references/repair.md`, `references/refactor.md`. - Resume/status: `references/continue.md`, `references/status.md`. - Verification: `references/verify.md`. - Integration: `references/finish.md`, `references/realign.md`. - Sync: `references/sync.md`, `references/realign.md`. - Consolidation: `references/realign.md`, `references/retention.md`. ## Run record Initialize operation/root/objective/source/scope; resume with current grants/session, preview by default. Specifications live in `docs/specs/`; `intent.md` binds approval. ADRs stay separate. New execution runs set `process_required: true`; use work-record's `references/process-runtime.md` to admit approved YAML and bind workers before dispatch. Preserve legacy unbound runs; require process/delivery/domain gates and reviewed commits. ## Canonical methods - Maps: `codebase-map:map-method`; dispatch isolated `codebase-map:map-analyst`. Own analyze preflight/checkpoints/delivery/publication; loading is not dispatch. - Load skills: `project-delivery:adr-method`. - Load skills: `research:science-based-approach` before substantive decisions; automatic checkpoint in caller run/grants. - Load skills: `senior-review:investigation-method`. - Load skills: `senior-review:review-method`; branches: `senior-review:review-preparation`. - Load skills: `senior-review:application-cleanup-method`. - Tests: `testing:test-preparation`, `testing:test-remediation-method`; dispatch `testing:test-writer`. - Load skills: `clean-code:readability-method`. - Load skills: `abstraction-architect:abstraction-architect` and its auditor. - Load skills: `project-knowledge:instructions-method`, `project-knowledge:project-knowledge`, `project-knowledge:readme-craft`. - Load skills: `repo-hygiene:repo-hygiene`. - Task workspaces/catalog: load skill `worktree-manager:worktree-method`. - Requested challenge: `peer-review:cross-model-peer-review`; dispatch `peer-review:packet-builder`, `peer-review:respondent`. Requested opinion: `moe:multi-model-deliberation`. - HTML: the coordinator must load skill `report-rendering:report-renderer` and read `references/project-run-view.md` before closure when requested/useful. Worktree method owns workspaces and catalog annotations; Work Controller owns agenda/grants. Status and brainstorming create none. Missing Worktrunk blocks dependent operations with its recovery path. ## Delivery and closure Validate `result.json`, retaining reports, hashes, gaps and shared-premise contradictions. Missing deliveries block completion. Separate inventory, reading and runtime with exact candidates/limits. Static checks are not runtime, self-checks not independent correctness, quarantine not recovered disk space.
Files in this package (25)
- SKILL.md 4 KB
- SKILL.toml 1 KB
- references/brainstorm.md 1 KB
- references/change.md 2 KB
- references/context-cycle.md 1 KB
- references/continue.md 2 KB
- references/document.md 1 KB
- references/finish.md 2 KB
- references/first-use.md 2 KB
- references/init.md 2 KB
- references/interview.md 2 KB
- references/investigate.md 1 KB
- references/preflight.md 4 KB
- references/realign.md 2 KB
- references/refactor.md 2 KB
- references/repair.md 2 KB
- references/retention.md 3 KB
- references/specification.md 2 KB
- references/status.md 1 KB
- references/sync.md 1 KB
- references/verify.md 2 KB
- references/waves.md 4 KB
- references/worker-brief.md 2 KB
- scripts/artifacts.py 20 KB
- scripts/cycle_packets.py 27 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · acaprino/alfio-claude-plugins | 90 | MIT |
| acaprino/alfio-claude-plugins | 100 | MIT |
| acaprino/alfio-claude-plugins | 100 | MIT |
| acaprino/alfio-claude-plugins | 100 | MIT |
| acaprino/alfio-claude-plugins | 100 | MIT |
| acaprino/alfio-claude-plugins | 100 | MIT |
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version a44bdbcba6f3 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100handover-method
Coordinate an evidence-based consultant intake dossier. TRIGGER WHEN: the user asks to be onboarded, walked through an unfamiliar codebase, given a project takeover or intake dossier, or runs /daodan:onboard-project. DO NOT TRIGGER WHEN: being new to a project is only background… - 100handover-method
Coordinate an evidence-based consultant intake dossier. TRIGGER WHEN: the user asks to be onboarded, walked through an unfamiliar codebase, given a project takeover or intake dossier, or runs /daodan:onboard-project. DO NOT TRIGGER WHEN: being new to a project is only background… - 100handover-method
Coordinate an evidence-based consultant intake dossier. TRIGGER WHEN: the user asks to be onboarded, walked through an unfamiliar codebase, given a project takeover or intake dossier, or runs /daodan:onboard-project. DO NOT TRIGGER WHEN: being new to a project is only background… - 100handover-method
Coordinate an evidence-based consultant intake dossier. TRIGGER WHEN: the user asks to be onboarded, walked through an unfamiliar codebase, given a project takeover or intake dossier, or runs /daodan:onboard-project. DO NOT TRIGGER WHEN: being new to a project is only background… - 100complete
Complete a finished feature, fix, or rollback by running final gates, archiving its spec, updating plans, creating the work commit, and requesting approval to land it locally or by pull request. Use for /complete or requests to finish, wrap up, merge, or close the current work item. - 100spec-finish
Post-implementation completion workflow for Spec-backed Plans. Use after spec-implement completes to validate, review, create stacked commits, and open a PR via code-pull-request. Triggers only with an active Spec-backed Plan after spec-implement completes, including when the…