Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

architect-status

Sterne3

Forks0

Aktualisiert11. Juli 2026 um 08:21

Report read-only Architect project status from core context and, when available, the tracks registry and plans. Use when the user asks for setup status, progress, current task, next action, blockers, completion percentage, or pending 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

hlhr202

hlhr202/swe-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	architect-status
description	Report read-only Architect project status from core context and, when available, the tracks registry and plans. Use when the user asks for setup status, progress, current task, next action, blockers, completion percentage, or pending work.

Architect Status

Report best-effort Architect state without changing it. Follow references/status-protocol.md as the source of truth.

Hard Boundaries

This skill is strictly read-only: never create, edit, move, delete, archive, or commit.
Keep reads under safe architect/ paths and never resolve malformed track links.
Report integrity issues; do not repair them.

Run

Read references/status-protocol.md and verify core context.
Classify missing, partial, or complete track-management state.
Parse safe registry entries, plans, and metadata best-effort.
Compute progress, current work, next action, blockers, and precedence-based project status.
Return the concise report and stop without mutations or interactive cleanup prompts.

Mehr aus diesem Repository

gleiches Repository

architect-implement

hlhr202/swe-skills

Implement or resume an existing Architect track by executing its approved plan and updating track status. Use when the user asks to implement, continue, resume, or complete a planned Architect track.

2026-07-163

architect-discuss

hlhr202/swe-skills

Use only when the user explicitly includes `architect-discuss` or directly asks to use the architect-discuss skill. Turns raw or ambiguous product and technical requirements into a product and architecture draft before tracked Architect proposal work.

2026-07-113

architect-propose

hlhr202/swe-skills

Propose and create a new Architect track for an initialized project, including its spec, plan, metadata, and registry entry. Use when the user asks to add, plan, or propose a new feature, bug fix, chore, refactor, docs, or test track.

2026-07-113

architect-review

hlhr202/swe-skills

Review Architect track work or explicit current changes against project context, track intent, style guides, and tests. Use when the user asks to review, verify, audit, inspect, approve, or apply review fixes for Architect-managed work.

2026-07-113

architect-setup

hlhr202/swe-skills

Initialize or resume Architect project setup by creating only the core architect/ context. Use when the user asks to set up Architect, scaffold Architect context, or recover an interrupted setup before discussion or proposal work.

2026-07-113

name	architect-status
description	Report read-only Architect project status from core context and, when available, the tracks registry and plans. Use when the user asks for setup status, progress, current task, next action, blockers, completion percentage, or pending work.

Architect Status

Report best-effort Architect state without changing it. Follow references/status-protocol.md as the source of truth.

Hard Boundaries

This skill is strictly read-only: never create, edit, move, delete, archive, or commit.
Keep reads under safe architect/ paths and never resolve malformed track links.
Report integrity issues; do not repair them.

Run

Read references/status-protocol.md and verify core context.
Classify missing, partial, or complete track-management state.
Parse safe registry entries, plans, and metadata best-effort.
Compute progress, current work, next action, blockers, and precedence-based project status.
Return the concise report and stop without mutations or interactive cleanup prompts.