Agent skill

gmacko-init-orchestrator

Use when (1) user wants a complete project setup from scratch, (2) one-command initialization of a new Gmacko Ventures project, (3) orchestrating the full init workflow. Coordinates interview, plan, bootstrap, and provision skills.

View SKILL.md on GitHub Repository
Stars 1
Forks 0

Install this agent skill to your Project

npx add-skill https://github.com/gmackie/vercel-expo-app-template/tree/main/.opencode/skill/gmacko-init-orchestrator

Metadata

Additional technical details for this skill

tier
orchestrator
phase
initialization
permission
ask

SKILL.md

Gmacko Init Orchestrator

One-button initialization: interview -> plan -> bootstrap -> provision -> validate.

Overview

This orchestrator coordinates the complete project initialization workflow by calling the appropriate skills in sequence. It provides a streamlined experience while maintaining the flexibility to skip or customize individual steps.

Workflow

dot
digraph orchestrator {
    rankdir=TB;
    node [shape=box];
    
    start [label="Start Orchestrator" shape=ellipse];
    check [label="1. Check Current State"];
    state [label="Determine Entry Point"];
    
    interview [label="2. gmacko-init-interview\n(Generate PROJECT_MANIFEST.json)"];
    plan [label="3. gmacko-init-plan\n(Generate INITIAL_PLAN.md)"];
    review [label="4. Review Plan with User"];
    approved [label="Approved?" shape=diamond];
    bootstrap [label="5. gmacko-init-bootstrap\n(Execute setup.sh)"];
    provision [label="6. gmacko-init-provision\n(Configure services)"];
    skip_provision [label="Skip provision?" shape=diamond];
    validate [label="7. Final Validation"];
    summary [label="8. Show Summary"];
    done [label="Orchestration Complete" shape=ellipse];
    
    start -> check -> state;
    state -> interview [label="no manifest"];
    state -> plan [label="manifest exists"];
    state -> bootstrap [label="plan exists"];
    
    interview -> plan -> review -> approved;
    approved -> bootstrap [label="yes"];
    approved -> interview [label="revise"];
    bootstrap -> skip_provision;
    skip_provision -> provision [label="no"];
    skip_provision -> validate [label="yes"];
    provision -> validate -> summary -> done;
}

Execution Steps

Step 1: Check Current State

Determine where to start based on existing artifacts:

bash
# Check what exists
HAS_MANIFEST=$([ -f "PROJECT_MANIFEST.json" ] && echo "true" || echo "false")
HAS_PLAN=$([ -f "INITIAL_PLAN.md" ] && echo "true" || echo "false")
HAS_BOOTSTRAP=$([ -f "docs/ai/handoffs/init-bootstrap.md" ] && echo "true" || echo "false")

Report state:

PROJECT STATE
=============
PROJECT_MANIFEST.json: [exists/missing]
INITIAL_PLAN.md: [exists/missing]
Bootstrap completed: [yes/no]

Ask user:

Based on the current state, I recommend starting from [step]. Would you like to: a) Start fresh (run full workflow) b) Continue from [recommended step] c) Skip to a specific step

Step 2: Run Interview (if needed)

If PROJECT_MANIFEST.json doesn't exist:

Starting project interview...

Invoke the gmacko-init-interview skill:

  • Complete all interview sections
  • Generate PROJECT_MANIFEST.json
  • Wait for manifest to be written

Step 3: Run Plan Generation (if needed)

If INITIAL_PLAN.md doesn't exist or manifest was just created:

Generating implementation plan...

Invoke the gmacko-init-plan skill:

  • Read PROJECT_MANIFEST.json
  • Generate INITIAL_PLAN.md
  • Create docs/ai/handoffs/init-plan.md

Step 4: Review Plan with User

Present plan summary and ask for approval:

I've generated your implementation plan. Here's the summary:

[Project Name]: [Description]

MVP Features:

  • [Feature 1]
  • [Feature 2]
  • [Feature 3]

Platforms: [Web/Mobile/Both] Integrations: [List enabled] Deployment: [Vercel/k8s] with [environments]

Please review INITIAL_PLAN.md for full details.

Ready to proceed with setup? (yes/revise/abort)

Step 5: Run Bootstrap (if approved)

If user approves:

Executing project setup...

Invoke the gmacko-init-bootstrap skill:

  • Run preflight checks
  • Execute scripts/setup.sh
  • Validate results

Step 6: Run Provision (optional)

After bootstrap completes:

Would you like to configure external services now? This will set up: [list enabled integrations]

a) Yes, configure all services b) Yes, but let me choose which ones c) Skip for now (I'll do it manually)

If user chooses to provision, invoke the gmacko-init-provision skill (to be created) or guide through scripts/provision.sh.

Step 7: Final Validation

Run comprehensive validation:

bash
# Full validation suite
pnpm typecheck
pnpm lint
pnpm build

# Check all handoffs exist
[ -f "docs/ai/handoffs/init-plan.md" ]
[ -f "docs/ai/handoffs/init-bootstrap.md" ]

Step 8: Show Summary

Present final summary:

INITIALIZATION COMPLETE
=======================

Project: [name] ([display name])
Repository: gmacko/[name]

Artifacts Created:
- PROJECT_MANIFEST.json (source of truth)
- INITIAL_PLAN.md (implementation roadmap)
- docs/ai/handoffs/init-plan.md
- docs/ai/handoffs/init-bootstrap.md

Services Configured:
- [x] Neon Database
- [x] Clerk Authentication
- [ ] Stripe Payments (skipped)
- [x] PostHog Analytics
- [x] Sentry Monitoring

Validation:
- Type check: PASSED
- Lint: PASSED
- Build: PASSED

NEXT STEPS
----------
1. Review INITIAL_PLAN.md with your team
2. Create GitHub repository:
   gh repo create gmacko/[name] --private --source=. --push
3. Set up Vercel project:
   vercel link
4. Start development:
   pnpm dev

Happy building!

Customization Options

Users can customize the orchestration:

Skip Interview (use existing manifest)

/gmacko-init-orchestrator --skip-interview

Skip Provision (manual setup later)

/gmacko-init-orchestrator --skip-provision

Dry Run (preview without changes)

/gmacko-init-orchestrator --dry-run

Error Recovery

If any step fails:

  1. Interview fails: Restart interview with saved progress (if partial manifest exists)
  2. Plan fails: Check manifest validity, regenerate
  3. Bootstrap fails: Check error, fix issue, retry bootstrap only
  4. Provision fails: Can be retried independently; other steps are complete

Red Flags

Rationalization Correction
"I'll skip the plan review" ALWAYS get user approval before bootstrap
"Bootstrap failed but I'll continue" STOP: Fix bootstrap before provision
"I'll run all steps without checking state" ALWAYS check existing artifacts first
"User seems impatient, I'll rush" Maintain quality; each step matters

Dependencies

This orchestrator invokes:

  1. gmacko-init-interview (Tier B)
  2. gmacko-init-plan (Tier B)
  3. gmacko-init-bootstrap (Tier B)
  4. gmacko-init-provision (Tier B, optional)

Handoff Document

After completion, ensure all handoffs are present:

  • docs/ai/handoffs/init-plan.md
  • docs/ai/handoffs/init-bootstrap.md
  • docs/ai/handoffs/init-provision.md (if provisioned)

Create summary handoff at docs/ai/handoffs/init-complete.md:

markdown
# Initialization Complete

## Timestamp
[ISO timestamp]

## Steps Completed
- [x] Interview (PROJECT_MANIFEST.json)
- [x] Plan (INITIAL_PLAN.md)
- [x] Bootstrap (setup.sh executed)
- [x/skipped] Provision (services configured)

## Validation
- Type check: PASSED
- Lint: PASSED
- Build: PASSED

## Ready for Development
The project is ready for feature implementation.
Start with Milestone 1 from INITIAL_PLAN.md.

Recommended Agent Skills

Expand your agent's capabilities with these related and highly-rated skills.

gmackie/vercel-expo-app-template

gmacko-dev-issue-create

Use when (1) creating GitHub issues from feature plans or bug reports, (2) documenting bugs found during development, (3) managing the project backlog. Creates well-structured GitHub issues with templates and labels.

1 0
Explore
gmackie/vercel-expo-app-template

gmacko-dev-pr-review

Use when (1) reviewing a pull request against coding standards, (2) verifying PR meets acceptance criteria from feature plan, (3) checking for common issues before merge. Reviews PRs against plan and project standards.

1 0
Explore
gmackie/vercel-expo-app-template

gmacko-release-prepare

Use when (1) preparing a release for staging or production, (2) generating release notes and changelog, (3) verifying environment readiness before deployment. Prepares all artifacts needed for a release.

1 0
Explore
gmackie/vercel-expo-app-template

gmacko-release-deploy-web

Use when (1) deploying web application to Vercel staging or production, (2) monitoring deployment progress, (3) running post-deployment verification. Manages Vercel deployment workflow with safety checks.

1 0
Explore
gmackie/vercel-expo-app-template

gmacko-init-plan

Use when (1) PROJECT_MANIFEST.json exists and you need to generate INITIAL_PLAN.md, (2) user wants a detailed implementation roadmap, (3) translating manifest into actionable milestones. Generates comprehensive project plan from the manifest.

1 0
Explore
gmackie/vercel-expo-app-template

gmacko-release-close

Use when (1) release is deployed and verified, (2) closing related issues and PRs, (3) creating GitHub release with changelog, (4) finalizing release documentation. Completes the release lifecycle.

1 0
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results