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

Phase Dev Rules

skill-zig999-siegard-code-phase-dev-rules · by zig999

Exit criteria checkers and worker routing table for the dev (implementation) phase. Consumed by orchestrator-dev.md to dispatch workers via select_worker.py and evaluate phase transition gates (check_all_impl_tasks_terminal, check_all_deliveries_qa_ready, check_no_open_prohibitions). Not user-invocable — orchestrators call scripts directly.

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

Install

$ agentstack add skill-zig999-siegard-code-phase-dev-rules

✓ 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-dev-rules)

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 Dev Rules? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

phase-dev-rules

Phase rules skill for the dev (implementation) phase. Provides exit criteria checkers and worker routing table consumed by orchestrator-dev.md.

Contract

The orchestrator calls this skill's scripts directly. No inter-skill communication envelope needed. Every script returns a JSON object to stdout and exits 0 on success or 1 on error.


Phase identity

| Field | Value | |-------|-------| | phase_name | dev | | order | 2 | | required | true | | worker_default | u-be-developer |


Worker routing table

Maps task.type + stack to worker sub-agent. Stack is resolved by orchestrator-dev from handoff-manifest.yaml before calling this script (Decision D2).

For fullstack projects, orchestrator-dev spawns two planning tasks with explicit split stacks (fullstack_be and fullstack_fe) so both planners run in parallel.

| task.type | stack | worker subagent_type | |-----------|-------|----------------------| | planning | be | u-be-planner | | planning | fe | u-fe-planner | | planning | fullstack_be | u-be-planner | | planning | fullstack_fe | u-fe-planner | | planning | fullstack | u-be-planner (legacy fallback) | | impl | be | u-be-developer | | impl | fe | u-fe-developer | | impl | fullstack | u-be-developer | | spec | be | u-be-developer | | spec | fe | u-fe-spec-writer | | spec | fullstack | u-fe-spec-writer | | * (default) | any | u-be-developer |


scripts/select_worker.py

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

Usage

python3 .claude/skills/phase-dev-rules/scripts/select_worker.py \
  --task-type  \
  --stack 

Output (exit 0)

{"worker": "u-be-developer", "task_type": "impl", "stack": "be", "phase": "dev"}

Error (exit 1, stderr)

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

Exit criteria

All three criteria must be met before the dev phase can transition. DLQ tasks block transition — a task in DLQ represents a failure, not a completed deliverable.

| Criterion | Script | Description | |-----------|--------|-------------| | all_impl_tasks_terminal | scripts/check_all_impl_tasks_terminal.py | All dev tasks in completed; zero DLQ tasks | | all_deliveries_qa_ready | scripts/check_all_deliveries_qa_ready.py | Every delivery.md has qa_ready: true | | no_open_prohibitions | scripts/check_no_open_prohibitions.py | No delivery.md has a non-empty prohibition_violations list |

See exit-criteria.json for the machine-readable declaration.

Environment variables

| Variable | Default | Description | |----------|---------|-------------| | ORCH_PROJECT_DIR | . | Project root — used to resolve delivery.md artifact paths |


scripts/checkallimpltasksterminal.py

Criterion: every task in the dev phase has status completed. DLQ tasks block the criterion (a failed task is not a deliverable). Not met if there are no dev tasks.

python3 .claude/skills/phase-dev-rules/scripts/check_all_impl_tasks_terminal.py

Output schema:

{
  "criterion": "all_impl_tasks_terminal",
  "met": true,
  "evidence": {
    "total": 10,
    "terminal": 10,
    "non_terminal": [],
    "dlq": [],
    "dlq_blocks_criterion": false
  }
}

scripts/checkalldeliveriesqaready.py

Criterion: every delivery.md artifact path listed in task_completed events for the dev phase contains the pattern qa_ready: true.

python3 .claude/skills/phase-dev-rules/scripts/check_all_deliveries_qa_ready.py

Output schema:

{
  "criterion": "all_deliveries_qa_ready",
  "met": true,
  "evidence": {
    "total": 5,
    "ready": 5,
    "not_ready": []
  }
}

met is false if no delivery artifacts are found (tasks completed with no artifacts).


scripts/checknoopen_prohibitions.py

Criterion: no delivery.md artifact contains a non-empty prohibition_violations list.

A prohibition violation is detected when the file contains the pattern: prohibition_violations: followed by at least one list item (- on the next non-blank line).

python3 .claude/skills/phase-dev-rules/scripts/check_no_open_prohibitions.py

Output schema:

{
  "criterion": "no_open_prohibitions",
  "met": true,
  "evidence": {
    "total": 5,
    "clean": 5,
    "violations": []
  }
}

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.