kiln-resume

Print a deprecation notice and delegate execution to kiln-next.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/yoshisada/ai-repo-template --skill kiln-resume
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kiln-resume
Source: https://github.com/yoshisada/ai-repo-template/tree/main/plugin-kiln/skills/kiln-resume
Command: npx skills add https://github.com/yoshisada/ai-repo-template --skill kiln-resume

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deprecated alias that prints a deprecation notice and delegates execution to the full /kiln:kiln-next workflow, preserving behavior while guiding users to the recommended path.

Core Features & Use Cases

  • Deprecated alias that triggers the kiln-next workflow
  • Prints the deprecation notice and delegates the entire workflow to kiln-next, including state gathering, classification, reporting, and backlog creation
  • Maintains parity with kiln-next outputs (terminal summary, persistent report, and backlog issues)

Quick Start

Execute kiln-resume to display the deprecation notice and automatically run kiln-next.

Frequently Asked Questions about kiln-resume

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I handle deprecated workflow automation requests during a tool migration?

Handling deprecated workflow automation requests during migration requires intercepting the old call, emitting a deprecation notice, and delegating execution to the replacement tool. This preserves consistent behavior, terminal summaries, and persistent reporting across existing project references.

What happens to my persistent reports and backlog creation when a workflow alias is deprecated?

When a workflow alias is deprecated, persistent reports and backlog creation are preserved by delegating execution to the replacement workflow. The deprecation notice prints first, then state gathering, classification, reporting, and backlog issues execute with full parity.

Can I migrate my DevOps automation to a new workflow without updating all project references?

Yes, you can migrate DevOps automation without updating references by using a deprecated alias that delegates execution to the replacement workflow. The alias emits a deprecation banner and automatically runs the new workflow, maintaining terminal summaries and persistent reports.

Why does my deprecated automation alias still run the full workflow instead of failing?

A deprecated automation alias still runs the full workflow instead of failing because it is designed to delegate execution to the replacement tool. It prints a deprecation notice and then triggers state gathering, classification, reporting, and backlog creation with full output parity.

Does the deprecation notice interrupt the workflow execution or terminal summary output?

The deprecation notice does not interrupt workflow execution or terminal summary output. It is emitted before delegating to the replacement workflow, ensuring the terminal summary, persistent report, and backlog creation proceed with consistent behavior and full output parity.