AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified Apache-2.0 Self-run

Phase Example

skill-zig999-siegard-code-phase-example · by zig999

Scaffold template for phase-{name}-rules skills. Copy the directory to phase-{name}-rules, replace {name} placeholders, implement the exit-criteria checkers and select_worker.py routing, and declare exit-criteria.json. Reference template only — never dispatched at runtime. Not user-invocable.

No reviews yet
0 installs
22 views
0.0% view→install

Install

$ agentstack add skill-zig999-siegard-code-phase-example

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-zig999-siegard-code-phase-example)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
2mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Phase Example? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

phase-{name}-rules

Phase rules skill for {name} phase. Provides exit criteria checkers, worker routing table, and phase-specific constraints consumed by the orchestrator.

Contract

Input (from orchestrator)

The orchestrator calls this skill's scripts directly. No inter-skill communication envelope needed.

Output

Every script in scripts/ returns a JSON object to stdout and exits 0 on success or 1 on error.


Phase identity

| Field | Value | |-------|-------| | phase_name | {name} | | order | {N} | | required | true | | worker_default | {worker-agent-name} |


Worker routing table

Maps task.type to worker sub-agent. Consumed by the orchestrator dispatcher (Step 5).

| task.type | worker subagent_type | |-----------|----------------------| | {type_a} | {worker-a} | | {type_b} | {worker-b} | | * (default) | {worker-default} |


scripts/select_worker.py

Returns the worker sub-agent name for a given task type.

Usage

python3 .claude/skills/phase-{name}-rules/scripts/select_worker.py \
  --task-type 

Output

On success (exit 0):

{"worker": "", "task_type": "", "phase": "{name}"}

On error (exit 1):

{"status": "error", "reason": "unknown_task_type", "detail": ""}

scripts/check{criterionname}.py

Evaluates one exit criterion. Replace {criterion_name} with the actual criterion identifier (e.g. all_impl_tasks_terminal, all_specs_approved, no_open_critical_findings).

One script per criterion. Each script is independent and has no side effects.

Usage

python3 .claude/skills/phase-{name}-rules/scripts/check_{criterion_name}.py

Output schema

{
  "criterion": "{criterion_name}",
  "met": true,
  "evidence": {
    "total": 0,
    "passing": 0,
    "failing": []
  }
}

| Field | Type | Description | |-------|------|-------------| | criterion | string | Criterion identifier (matches key in exit-criteria.json) | | met | bool | true if criterion is satisfied | | evidence | object | Supporting data — structure varies by criterion |

On error (exit 1):

{"status": "error", "reason": "", "detail": ""}

Error reason codes:

  • log_missing.orch/log.jsonl not found
  • internal_error — unexpected runtime error

exit-criteria.json

Declares all exit criteria for this phase. The orchestrator evaluates each criterion by calling the corresponding check_{criterion_id}.py script.

See exit-criteria.json in this directory.


references/

Phase-specific reference documents. Optional — add files here when the phase has domain-specific rules, templates, or vocabulary that workers need to consume.

| File | Purpose | |------|---------| | (empty in this template) | (add as needed) |

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.