determine-next-steps

Generate a CRISP-DM 5.3 go/no-go decision document from 5.1 and 5.2 outcomes.

Updated Mar 20, 2026
One-click install
npx skills add https://github.com/thbraet/claude-template --skill determine-next-steps
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: determine-next-steps
Source: https://github.com/thbraet/claude-template/tree/main/skills/determine-next-steps
Command: npx skills add https://github.com/thbraet/claude-template --skill determine-next-steps

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Synthesizes results evaluation and process review into a go/no-go decision document for CRISP-DM 5.3.

Core Features & Use Cases

  • Produces a formal decision (Deploy / Iterate / Terminate) based on inputs from 5.1 and 5.2
  • Generates a structured artifact at docs/crisp-dm/5-evaluation/5.3-determine-next-steps.md
  • Supports traceability by referencing source documents (5.1, 5.2, 1.x business docs, 4.4 model assessment)

Quick Start

Please determine the next steps for the project by analyzing outputs from 5.1 and 5.2 and generate a formal 5.3 decision document.

Frequently Asked Questions about determine-next-steps

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

FAQPage Schema
How do I create a go/no-go decision document for a data analytics project?

To create a go/no-go decision document, synthesize results evaluation and process review inputs to determine whether to Deploy, Iterate, or Terminate. This generates a structured Markdown file with sections for rationale, actions, and stakeholder approvals.

What is CRISP-DM 5.3 determine next steps in project governance?

CRISP-DM 5.3 determine next steps is the evaluation phase that synthesizes 5.1 results and 5.2 process reviews into a formal Deploy, Iterate, or Terminate decision. It produces a traceable artifact stored under the evaluation documentation directory.

How do I decide whether to deploy, iterate, or terminate a machine learning model?

To decide whether to deploy, iterate, or terminate, analyze outputs from results evaluation and process review phases alongside business objectives and model assessments. This synthesis forms the rationale for a formal project governance decision document.

Can I use CRISP-DM evaluation outputs to generate a stakeholder approval document?

Yes, CRISP-DM evaluation outputs from 5.1 and 5.2 can be synthesized into a structured Markdown document featuring dedicated sections for inputs, rationale, actions, and approvals suitable for stakeholder review.

What inputs are required for the CRISP-DM determine next steps phase?

The CRISP-DM determine next steps phase requires inputs from the 5.1 results evaluation, 5.2 process review, 1.x business documents, and 4.4 model assessment to ensure traceability and support the final decision.

Where should CRISP-DM 5.3 decision artifacts be stored?

CRISP-DM 5.3 decision artifacts should be stored under docs/crisp-dm/5-evaluation as a structured Markdown file, specifically named 5.3-determine-next-steps.md, to maintain project governance and traceability.