Triage post-feature requests into lightweight, partial restart, or full restart paths.
npx skills add https://github.com/NachoFLizaur/corvus --skill corvus-phase-7
Please help me install this Agent Skill. Skill: corvus-phase-7 Source: https://github.com/NachoFLizaur/corvus/tree/main/skill/corvus-phase-7 Command: npx skills add https://github.com/NachoFLizaur/corvus --skill corvus-phase-7
Follow-up triage after a feature is completed to assess new user requests and route them without breaking workflow integrity.
Begin by evaluating the new request against triage criteria and selecting the appropriate path (LIGHTWEIGHT PATH, PARTIAL RESTART, or FULL RESTART) to initiate the triage.
High-intent search queries and answers about installing and using this skill.
Post-delivery follow-up triage applies a decision tree to assess new requests and route them safely. It evaluates whether incoming changes are lightweight tweaks, require partial restarts, or necessitate full restarts to maintain ongoing product workflow alignment.
Routing lightweight tweaks versus full restarts requires selecting the appropriate triage path based on request scope. The process categorizes post-delivery changes into lightweight paths, partial restarts, or full restarts to ensure consistent handling and documentation.
Task routing procedures for post-delivery changes are needed whenever users request modifications within the same session after feature completion. Triage decision logic determines if the request requires a lightweight tweak, partial restart, or full restart.
Documenting follow-up assessments involves capturing the request, scope, and routing rationale. The triage process updates plan references and task status, ensuring traceability and consistent documentation of whether a lightweight, partial, or full restart path was chosen.
Yes, this follow-up triage process specifically handles post-delivery requests within the same session. It applies structured assessment data collection and task routing procedures to manage lightweight tweaks and restarts without disrupting workflow integrity.
Automated triage decision trees for follow-ups are limited to post-delivery requests within the same session. They enforce routing logic for lightweight tweaks and restarts but do not replace broader product management planning for entirely new features.
featbitTransform vague user inputs into measurable business goals within project constraints.
scitixDiagnose Volcano batch job statuses and issues using kubectl.
AhmedElhadareySynchronize stale business documentation when track decisions change.
ericfitzTranslate English text to a target language while preserving placeholders and formatting.
