assess-method
/assess-method
Diagnose project coherence and technical debt through canonical specialist audits and an executable roadmap. TRIGGER WHEN: the user asks for project health, a coherence assessment, technical-debt diagnosis or a prioritized maintenance roadmap, including /daodan:check-health and the assessment stage of /daodan:run-maintenance. DO NOT TRIGGER WHEN: implementing an approved change, repair or verification cycle (use project-delivery:delivery-method), running a full Senior Maintainer campaign (use maintainer-method), or preparing a consultant dossier (use handover-method).
- Author
- acaprino ↗
- Repository
- alfio-claude-plugins ↗
- Licence
- MIT
- Last repository change
- 27.10.2026
Assessment and security
- Files in this package
- 5
- Scripts
- 1
- 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.
- 1 scripts in this package. Review them before installing, as Claude may execute them.
Scripts: scripts/native_reports.py
What it does and when to use it
Diagnose project coherence and technical debt through canonical specialist audits and an executable roadmap. TRIGGER WHEN: the user asks for project health, a coherence assessment, technical-debt diagnosis or a prioritized maintenance roadmap, including /daodan:check-health and the assessment stage of /daodan:run-maintenance. DO NOT TRIGGER WHEN: implementing an approved change, repair or verification cycle (use project-delivery:delivery-method), running a full Senior Maintainer campaign (use maintainer-method), or preparing a consultant dossier (use handover-method).
Original author description
Diagnose project coherence and technical debt through canonical specialist audits and an executable roadmap. TRIGGER WHEN: the user asks for project health, a coherence assessment, technical-debt diagnosis or a prioritized maintenance roadmap, including /daodan:check-health and the assessment stage of /daodan:run-maintenance. DO NOT TRIGGER WHEN: implementing an approved change, repair or verification cycle (use project-delivery:delivery-method), running a full Senior Maintainer campaign (use maintainer-method), or preparing a consultant dossier (use handover-method).
How it works
SKILL.md has no level-two headings · 95 lines, 848 words
SKILL.md preview
--- name: assess-method description: > Diagnose project coherence and technical debt through canonical specialist audits and an executable roadmap. TRIGGER WHEN: the user asks for project health, a coherence assessment, technical-debt diagnosis or a prioritized maintenance roadmap, including /daodan:check-health and the assessment stage of /daodan:run-maintenance. DO NOT TRIGGER WHEN: implementing an approved change, repair or verification cycle (use project-delivery:delivery-method), running a full Senior Maintainer campaign (use maintainer-method), or preparing a consultant dossier (use handover-method). --- <daodan_host_binding host="opencode"> This binding governs execution of this package and its loaded references. It takes precedence over executable examples written for another host. Use only registered tools and their actual input schema; an example never creates a tool, argument, permission, model alias or nested worker capability. Preserve the generated worker allowlist, dependency closure, scope and delivery contracts. OpenCode V2 binding: repository reads use read/glob/grep, writes use write/edit/patch, shell execution uses shell, network tools are webfetch/websearch, and clarification uses the registered question tool. shell takes command, optional workdir, timeout in milliseconds and background. It does not provide interactive stdin. Persistent capture uses background: true and an explicit noninteractive stop signal. Load skills with skill using id: "<plugin>:<skill>". Dispatch registered roles with subagent using agent: "<owner>:<role>", description and prompt; optional sessionID continues that child, and background: true requests asynchronous completion. Use only roles allowed by the current harness and permissions. A child cannot dispatch nested workers when its permissions or the configured depth deny it. Workflow entries are /<plugin>:<workflow>, registered by the package loader. Inherit the session model; an override requires its authorized, actually available provider/model identity, not another host's short model alias. The loader includes required local providers and registers plugin-declared MCP servers. Qualified foreign providers need a compatible V2 plugin/skill provisioned through this host, never a Claude marketplace command. Check the active registry: registration metadata alone does not prove a connected server or usable tool. Inherit the active session's model and default variant. A source model alias such as sonnet is not a portable override; request a different model only through an explicit adapter mapping to a valid host identity and user authorization. The executing agent and its coordinator own continuation, recovery, verification and delivery. Skills supply knowledge and method instructions; they are not executors or a runtime persistence mechanism. Resolve each component by kind and exact installed identity. A role is dispatched as a worker, a skill loads instructions, and a workflow starts its declared method. Kernel owner-qualified skill references are logical provider identities: resolve them to the actual host registry name and verified installed provider path. Do not invent a registry string by adding an owner's prefix when the host does not use it. Do not load an agent identity as a skill or execute a workflow name as a shell command. Declared required foreign providers remain mandatory. If a required provider or capability (including required MCP access or isolation) is unavailable, stop its dependent phase and report the missing capability. Optional external providers follow the method's declared selection and absence behavior; their absence alone does not block the base workflow. Report any explicitly requested but unavailable provider contribution as unfulfilled and continue independent work. Do not install a different host's plugin or substitute unrelated skills to claim coverage. Shell execution alone does not establish interactive stdin. Before a capture or checkpoint, use an available session-control mechanism. When stdin is unavailable, keep user-driven capture in a supported background process with bounded output and an explicit stop signal controlled by the coordinator after the user's completion message. Close owned browser/process resources on completion or cancellation. Continue working within the current authorization while the requested result is achievable. After a tool error, inspect its cause, correct the relevant input or implementation, retry when justified and verify the outcome; never repeat a failing action blindly. Do not close the turn with a promise or a partial result when an authorized next step can still produce or verify the requested result. Stop only for a documented real impediment, a missing required capability, an unresolved human decision or the caller's stop request. At that boundary, report completed results, remaining work and the concrete prerequisite for continuation; continue any independent work that the blocker does not prevent. A tool's successful exit, a worker stop or an idle session is not the deliverable. Return final text naming observed findings, artifact paths, executed checks and blockers. An empty worker result is missing delivery: inspect or resume that worker when permitted, or record failure. Verify required artifacts and candidate gates before marking the requested outcome complete. This is an execution binding, not a rewrite of source examples. Preserve programming language fences, domain code and host APIs that are the subject of marketplace-ops or agent-sdk-builder. A host-as-subject API is not a tool provided to this session. Compiled binding and static checks do not prove an installed host executed a run. </daodan_host_binding> # Project assessment Load skill `work-controller:work-record` for run ownership, snapshots, authorization, delivery accounting and result validation. Assessment is read-only for product and durable project files; only run-owned reports and an explicit Codebase Map run are permitted outputs. Read `references/assess.md` before selecting or dispatching auditors. Load `codebase-map:map-method` and dispatch `codebase-map:map-analyst` in an isolated context as that unit directs. Keep each specialist's native report, exact candidate and declared gaps. Consolidate an executable roadmap without turning coherence findings into a correctness verdict. Implementation, repair, verification and consolidation after the assessment belong to `project-delivery:delivery-method`. For native result wrappers and workspace dispositions, read `references/native-reports.md`. Before closing, the coordinator loads any requested HTML view through skill `report-rendering:report-renderer` and reads its `references/project-run-view.md`.
Files in this package (5)
- SKILL.md 7 KB
- SKILL.toml 1 KB
- references/assess.md 10 KB
- references/native-reports.md 6 KB
- scripts/native_reports.py 2 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · acaprino/alfio-claude-plugins | 91 | MIT |
| acaprino/alfio-claude-plugins | 91 | MIT |
| acaprino/alfio-claude-plugins | 91 | MIT |
| acaprino/alfio-claude-plugins | 91 | MIT |
| acaprino/alfio-claude-plugins | 91 | MIT |
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version 23f5b4ab64db (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
- 95maintainer-method
Coordinate the complete Senior Maintainer rationalization campaign. TRIGGER WHEN: the user wants a whole project brought back into good shape through a coordinated multistage campaign, or runs /daodan:run-maintenance. DO NOT TRIGGER WHEN: an intake dossier is sufficient (use… - 85maintainer-method
Coordinate the complete Senior Maintainer rationalization campaign. TRIGGER WHEN: the user wants a whole project brought back into good shape through a coordinated multistage campaign, or runs /daodan:run-maintenance. DO NOT TRIGGER WHEN: an intake dossier is sufficient (use… - 95maintainer-method
Coordinate the complete Senior Maintainer rationalization campaign. TRIGGER WHEN: the user wants a whole project brought back into good shape through a coordinated multistage campaign, or runs /daodan:run-maintenance. DO NOT TRIGGER WHEN: an intake dossier is sufficient (use… - 85maintainer-method
Coordinate the complete Senior Maintainer rationalization campaign. TRIGGER WHEN: the user wants a whole project brought back into good shape through a coordinated multistage campaign, or runs /daodan:run-maintenance. DO NOT TRIGGER WHEN: an intake dossier is sufficient (use… - 100tech-debt-assessment
Use when the user wants technical debt inventoried or prioritized: tech debt, code health, refactoring priorities, or a cleanup roadmap. - 95risk-assessment
Assess project/domain health — scan risk zones across dimensions (bugs, hotspots, tech debt). Use when asked evaluate risks, find problematic areas, assess code health, identify zones needing attention — NOT for specific bug symptoms (use bug-hunt instead)