AgentStack
Sign in Publish
MCP servers Skills Toolkits Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Execute Build

skill-martian56-claude-engineer-execute-build · by martian56

Use after the plan is signed off, to drive the autonomous, plan-gated build to completion. Orchestrates per-task implementation, review, and verification in customer-experience-first order, stopping only on genuine blockers.

↗ Repository
— No reviews yet
0 installs
8 views
0.0% view→install

Install

$ agentstack add skill-martian56-claude-engineer-execute-build

✓ 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.

Are you the author of Execute Build? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Execute Build

Announce at start: "I'm using claude-engineer:execute-build to drive the autonomous build."

Iron Law

Only run after the user signed off on the plan (claude-engineer:plan-project). If there is no signed-off plan in docs/plan/, stop and go back.

The drive loop

  1. Read state first (.claude-engineer/memory.md, progress.md, current-phase.txt). Trust them over recollection.
  2. Isolate the workspace via superpowers:using-git-worktrees before writing code.
  3. Work phases in CX-first order (from the plan): Phase 0 scaffold → 1 design system → 2 frontend → 3 backend → 4 integration → 5 quality/CI/finish. Invoke the matching claude-engineer domain skill for each phase:
  • project-conventions, monorepo-and-tooling, docker-dev-environment (scaffold)
  • design-system → frontend-development → backend-development
  • testing-and-quality, ci-cd-pipeline
  1. Execute tasks with superpowers:subagent-driven-development - a fresh implementer subagent per task; each task uses superpowers:test-driven-development. Use superpowers:dispatching-parallel-agents for independent workstreams. Fall back to superpowers:executing-plans only where subagents are unavailable.
  2. After each task: update .claude-engineer/progress.md; record decisions in memory.md.
  3. When something breaks: superpowers:systematic-debugging (root cause before fixes).
  4. Review gate per phase / major feature: superpowers:requesting-code-review + superpowers:receiving-code-review.
  5. Before claiming any phase "done": superpowers:verification-before-completion AND run the four gates via claude-engineer:testing-and-quality.
  6. Finish: claude-engineer:ci-cd-pipeline then superpowers:finishing-a-development-branch.

Autonomy & stopping

Plan-gated then autonomous: run to completion without check-ins. Stop only on genuine blockers - ambiguous requirements not covered by the brief, a destructive/irreversible action, missing credentials, or a decision that changes the agreed plan. Surface the blocker crisply with options.

Red flags - STOP

  • Building before reading the ledger → re-read it.
  • Re-doing a task already marked done in progress.md.
  • Marking a phase done without running the four gates.
  • Changing the plan unilaterally → that's a blocker; ask.

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.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Agent Skills