Skip to content
Skills Library
Management & product · Analysis

kata-progress

/kata-progress

Use when the user asks for Kata project status, milestone progress, task progress, or execution state.

Repository
kata ↗
Licence
MIT
Last repository change
02.09.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
9
Scripts
2
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 02.09.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What to check before installing
  • 2 scripts in this package. Review them before installing, as Claude may execute them.

Scripts: scripts/kata-artifact-input.mjs, scripts/kata-call.mjs

What it does and when to use it

Use when the user asks for Kata project status, milestone progress, task progress, or execution state.

Original author description

Use when the user asks for Kata project status, milestone progress, task progress, or execution state.

How it works

  1. Operating Brief
  2. Success Criteria
  3. Do Not
  4. Process
  5. Resource Loading
  6. Execution Rules
Original SKILL.md headings · 58 lines, 315 words
SKILL.md preview
---
name: kata-progress
description: "Use when the user asks for Kata project status, milestone progress, task progress, or execution state."
---

# kata-progress

## Operating Brief

When this skill is invoked, report current Kata project and milestone progress.

Read the project snapshot plus execution status. Summarize what is active, what is blocked, what is done, and the one next action recommended by snapshot state.

This is a reporting skill. It should not mutate backend state.

## Success Criteria

- The user sees the current project/backend identity.
- The active milestone, slices, tasks, artifacts, and execution state are summarized.
- Blocking issues and next actions are clear.
- No backend state is changed.

## Do Not

- Do not create or update project artifacts.
- Do not change task or milestone status.
- Do not proceed into execution from a status request.
- Do not omit blockers or warnings.

## Process

1. Read `references/workflow.md` before taking action. Execute that workflow end-to-end.
2. Preserve every workflow gate: required checks, user confirmations, durable writes, status updates, and next-step routing.
3. Before any backend IO, read `references/runtime-contract.md` and use only the operations listed there.
4. When the workflow tells you to create or read an artifact, use `references/artifact-contract.md` and the named template files.
5. If setup or backend readiness is uncertain, read `references/setup.md` before proceeding.
6. Read optional references only when the workflow calls for them or the current step needs them.

## Resource Loading

Must read:

- Workflow: `references/workflow.md`
- Runtime IO contract: `references/runtime-contract.md`

Read when needed:

- Setup and health checks: `references/setup.md`
- Alignment depth: `references/alignment.md`
- CLI command patterns: `references/cli-runtime.md`
- Artifact conventions: `references/artifact-contract.md`
- CLI helper: `scripts/kata-call.mjs`
- Artifact input helper: `scripts/kata-artifact-input.mjs`

## Execution Rules

1. If setup or backend state is uncertain, start with `references/setup.md`.
2. Choose alignment depth using `references/alignment.md` inside this workflow.
3. Follow `references/workflow.md` as the behavioral source for this skill.
4. Use only operations listed in `references/runtime-contract.md` for backend IO.
5. Keep backend specifics in @kata-sh/cli adapters, never in skill logic.
Files in this package (9)
  • SKILL.md 2 KB
  • references/alignment.md 1 KB
  • references/artifact-contract.md 6 KB
  • references/cli-runtime.md 7 KB
  • references/runtime-contract.md 1 KB
  • references/setup.md 1 KB
  • references/workflow.md 3 KB
  • scripts/kata-artifact-input.mjs 2 KB
  • scripts/kata-call.mjs 3 KB

Versions

The database has no other skills named kata-progress.

Database snapshot: 13.11.2026 · package version 09b52dae1bd6 (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

  • 90kata-plan-phase
    Use when the user asks to plan a phase, slice upcoming work, or turn a milestone goal into executable Kata tasks.
  • 90kata-new-milestone
    Use when the user wants to create the next milestone, release goal, or scoped delivery target for an existing Kata project.
  • 90milestone-status-extractor
    Extracts the current status of every project milestone mentioned in email — what has been completed, what is in progress, what is at risk, and what is overdue. Use when a project manager needs a milestone status view from email without updating a project management tool…
  • 100client-update
    Write a status update or milestone report for whoever is waiting on the work - a client, or the person you answer to inside a company. Trigger on "update the client", "write a status update", "write my status update", "project update", "send a progress report", "milestone…
  • 96status
    Use when checking feature progress or wanting to see what features exist and their current status
  • 84save-progress
    Save current project task progress to local task state file for cross-session continuity. Use when the user asks to save progress, uses an equivalent localized trigger phrase, the session is interrupted, or the user wants to resume work later. Writes to…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.