Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

zno-status

Sterne2

Forks0

Aktualisiert2. Juli 2026 um 15:34

Use when the user writes /zno-status, wants to save current progress before switching or ending a session, or asks for a progress snapshot. Inspects the workspace and writes a factual, handoff-ready snapshot to docs/development/10-current-status.md. Does not implement new work.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

1447751897

1447751897/ai-project-command-skills

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

Datei-Explorer

2 Dateien

SKILL.md

readonly

name	zno-status
description	Use when the user writes /zno-status, wants to save current progress before switching or ending a session, or asks for a progress snapshot. Inspects the workspace and writes a factual, handoff-ready snapshot to docs/development/10-current-status.md. Does not implement new work.

Zno-Status — Progress Snapshot

<skills-root> below means the directory containing all zno-* skills (e.g. ~/.claude/skills or ~/.agents/skills).

Workflow

Inspect the current state: relevant docs, and git status / recently changed files when available.

If docs/development/10-current-status.md does not exist yet, scaffold it first:

python <skills-root>/zno-init/scripts/init_project_docs.py <project-root> --scaffold status

Record in the status doc: current phase, current task, completed work, in-progress work, pending next steps, blockers, recent file changes, what verification ran, what verification did NOT run, and continuation advice.
Keep the snapshot strictly factual. Never claim tests ran unless they actually ran.
Do not implement new work unless the user explicitly asks.
Final response: confirm the snapshot was updated and state the recommended next step (usually /zno-continue in the next session).

Shared references (read only when needed)

<skills-root>/zno-init/references/docs-map.md — full doc set, doc update rules, scaffold triggers.

Mehr aus diesem Repository

gleiches Repository

zno-change

1447751897/ai-project-command-skills

Use when the user writes /zno-change or asks to change existing behavior or scope in an ongoing project. Identifies the affected docs and code before implementing, updates them together with the change, and records the change in the feature changelog.

2026-07-022

zno-continue

1447751897/ai-project-command-skills

Use when the user writes /zno-continue or starts a new session wanting to resume where a previous conversation left off. Reads the status snapshot and supporting docs, summarizes the project state, then continues with the next safe task.

2026-07-022

zno-deploy

1447751897/ai-project-command-skills

Use when the user writes /zno-deploy or asks about deployment, release, environments, migration, or rollback. Plans and executes the deployment change, updates docs/operations/08-deployment.md, and updates local-development docs when commands or env vars change.

2026-07-022

zno-evaluate

1447751897/ai-project-command-skills

Use when the user writes /zno-evaluate or wants to validate whether a project idea is worth doing before committing. Uses Socratic questioning to challenge the idea across pain points, target users, existing solutions, ROI, risks, and timeline. Outputs a structured evaluation conclusion (do / don't do / defer). Should be used before /zno-init.

2026-07-022

zno-feature

1447751897/ai-project-command-skills

Use when the user writes /zno-feature or asks to add a new feature to an ongoing project. Clarifies only what affects scope or design, follows TDD when a test framework exists, updates the relevant docs and the feature changelog, and passes the verification gate before completion.

2026-07-022

zno-fix

1447751897/ai-project-command-skills

Use when the user writes /zno-fix or reports a bug or defect. Reproduces or reasons about the defect, locates the root cause, fixes it with a regression test when possible, verifies the fix, and updates the changelog if behavior changed.

2026-07-022

name	zno-status
description	Use when the user writes /zno-status, wants to save current progress before switching or ending a session, or asks for a progress snapshot. Inspects the workspace and writes a factual, handoff-ready snapshot to docs/development/10-current-status.md. Does not implement new work.

Zno-Status — Progress Snapshot

<skills-root> below means the directory containing all zno-* skills (e.g. ~/.claude/skills or ~/.agents/skills).

Workflow

Inspect the current state: relevant docs, and git status / recently changed files when available.

If docs/development/10-current-status.md does not exist yet, scaffold it first:

python <skills-root>/zno-init/scripts/init_project_docs.py <project-root> --scaffold status

Record in the status doc: current phase, current task, completed work, in-progress work, pending next steps, blockers, recent file changes, what verification ran, what verification did NOT run, and continuation advice.
Keep the snapshot strictly factual. Never claim tests ran unless they actually ran.
Do not implement new work unless the user explicitly asks.
Final response: confirm the snapshot was updated and state the recommended next step (usually /zno-continue in the next session).

Shared references (read only when needed)

<skills-root>/zno-init/references/docs-map.md — full doc set, doc update rules, scaffold triggers.