journey-template

Name: journey-template
Author: DanWahlin

36stars10forks

How to install journey-template?

danwahlin/github-azure-agentic-journeys/journey-template

$npx -y skills add DanWahlin/github-azure-agentic-journeys --skill journey-template

Installs into the current project.

Summary

Create new agentic journeys from app ideas. Generates README.md (learner walkthrough), PLAN.md (AI-readable spec), and app-specific skills for OSS deployments. Supports any stack (Node.js, Python, .NET, Java, Swift, Kotlin) and Azure service (Container Apps, AKS, Functions, App S

Files · 1

View on GitHub

SKILL.md

1	# Journey Template Skill
2
3	Generate a complete agentic journey from a user's app idea. A journey is a hands-on learning experience where developers use GitHub Copilot (CLI, app, or IDE) to build and deploy an app to Azure.
4
5	## Curriculum packaging (required)
6
7	Every journey README must include:
8	- No learning-path or stage numbering — journeys are self-contained; link related journeys in What's Next
9	- Honest first-run time + cost if left running + same-day teardown
10	- Done when checklist with concrete manual verification steps
11	- Full-stack: one-line default stack at the first generate prompt (not a defaults table); put stack details in PLAN.md
12	- Plugin commands: only `microsoft/azure-skills` / `azure@azure-skills`
13	- What's Next aligned to the path (not renumbered leftovers)
14	- OSS: shared deploy recipe (location, secrets, probes, resolve issues, issues.md)
15
16	Update root `README.md` learning path + journey table when adding a journey.
17
18	## Journey Types
19
20	\| Dimension \| Full-Stack (e.g. AIMarket) \| OSS Deployment (e.g. n8n, Grafana, Superset) \|
21	\|-----------\|---------------------------\|----------------------------------------------\|
22	\| What the learner does \| Builds an app from scratch with GitHub Copilot \| Deploys an existing OSS app via `@oss-to-azure-deployer` agent \|
23	\| Files generated \| README.md + PLAN.md \| README.md + app-specific skill in `.github/skills/` \|
24	\| README structure \| "The Journey" with 3-5 phases (adapt to app complexity) \| "Deploy with the Agent" with 3 steps (Setup → Deploy → Verify) \|
25	\| Time \| 3–5 hours first run (say 2–3 only if re-run) \| 15–45 minutes first run \|
26	\| Images \| 4-6 (one per phase boundary) \| 2 (hero + deployment) \|
27	\| Unique sections \| "The Spec", "How Agentic AI is Used", one-line default stack at first prompt \| "Configuration Reference", "Key Learnings", skip rules if expensive \|
28	\| Compute target \| Container Apps, App Service, Functions, Static Web Apps, AKS \| Container Apps, AKS, App Service \|
29
30	## Output Structure
31
32	```
33	journeys/<app-name>/
34	├── README.md # Learner-facing walkthrough
35	├── PLAN.md # AI-readable spec (full-stack journeys only)
36	└── images/ # Generated images (added separately)
37	```
38
39	For OSS deployment journeys, also create an app-specific skill:
40
41	```
42	.github/skills/<app>-azure/
43	├── SKILL.md # Overview, quick start, architecture, verification
44	├── config/
45	│ ├── environment-variables.md
46	│ └── health-probes.md
47	└── troubleshooting.md
48	```
49
50	The SKILL.md needs YAML frontmatter:
51
52	```yaml
53	---
54	name: <app>-azure
55	description: Deploy <App> to Azure. Use when deploying <App> for <purpose>.
56	---
57	```
58
59	### OSS Skill SKILL.md Structure
60
61	The skill is what the `@oss-to-azure-deployer` agent reads. Follow this section order (reference `n8n-azure` as the primary example):
62
63	1. Overview / When to Use — one paragraph
64	2. Critical: Infrastructure Generation — infrastructure is generated fresh each deployment via `azure-prepare` plugin, NOT committed to the repo
65	3. Critical: Subscription Context — read the value with `az account show --query id -o tsv`, then pass it to `azd env set AZURE_SUBSCRIPTION_ID <subscription-id>` without shell command substitution
66	4. Critical: \<App-Specific Gotcha\> — the #1 deployment failure cause (e.g., PostgreSQL SKU needs both `name` AND `tier`; Bicep outputs MUST use SCREAMING_SNAKE_CASE)
67	5. Official Documentation — link to app's docs
68	6. Quick Start (Verified) — exact prompt sequence, tested and confirmed
69	7. Key Configuration Files — table pointing to `config/environment-variables.md`, `config/health-probes.md`, `troubleshooting.md`
70	8. Architecture — Mermaid diagram of Azure resources
71	9. App-Specific Requirements — database, networking, storage, ports
72	10. Cost Estimate — table with SKUs and monthly costs
73	11. Verification Checklist — curl / az commands to confirm deployment
74	12. Tear Down — `azd down --force --purge`
75	13. Differences from Generic Patterns — what makes this app non-standard (startup timing, SSL, env vars, ports)
76
77	For AKS-based apps (like Superset), also include:
78	- `references/kubernetes-manifests.md` in the skill directory
79	- Default credentials section (e.g., admin/admin)
80	-

People who liked this also viewed

6 picks

Type

journey-template

36stars10forks

View on GitHub

How to install journey-template?

danwahlin/github-azure-agentic-journeys/journey-template

$npx -y skills add DanWahlin/github-azure-agentic-journeys --skill journey-template

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Journey Template Skill
2
3	Generate a complete agentic journey from a user's app idea. A journey is a hands-on learning experience where developers use GitHub Copilot (CLI, app, or IDE) to build and deploy an app to Azure.
4
5	## Curriculum packaging (required)
6
7	Every journey README must include:
8	- No learning-path or stage numbering — journeys are self-contained; link related journeys in What's Next
9	- Honest first-run time + cost if left running + same-day teardown
10	- Done when checklist with concrete manual verification steps
11	- Full-stack: one-line default stack at the first generate prompt (not a defaults table); put stack details in PLAN.md
12	- Plugin commands: only `microsoft/azure-skills` / `azure@azure-skills`
13	- What's Next aligned to the path (not renumbered leftovers)
14	- OSS: shared deploy recipe (location, secrets, probes, resolve issues, issues.md)
15
16	Update root `README.md` learning path + journey table when adding a journey.
17
18	## Journey Types
19
20	\| Dimension \| Full-Stack (e.g. AIMarket) \| OSS Deployment (e.g. n8n, Grafana, Superset) \|
21	\|-----------\|---------------------------\|----------------------------------------------\|
22	\| What the learner does \| Builds an app from scratch with GitHub Copilot \| Deploys an existing OSS app via `@oss-to-azure-deployer` agent \|
23	\| Files generated \| README.md + PLAN.md \| README.md + app-specific skill in `.github/skills/` \|
24	\| README structure \| "The Journey" with 3-5 phases (adapt to app complexity) \| "Deploy with the Agent" with 3 steps (Setup → Deploy → Verify) \|
25	\| Time \| 3–5 hours first run (say 2–3 only if re-run) \| 15–45 minutes first run \|
26	\| Images \| 4-6 (one per phase boundary) \| 2 (hero + deployment) \|
27	\| Unique sections \| "The Spec", "How Agentic AI is Used", one-line default stack at first prompt \| "Configuration Reference", "Key Learnings", skip rules if expensive \|
28	\| Compute target \| Container Apps, App Service, Functions, Static Web Apps, AKS \| Container Apps, AKS, App Service \|
29
30	## Output Structure
31
32	```
33	journeys/<app-name>/
34	├── README.md # Learner-facing walkthrough
35	├── PLAN.md # AI-readable spec (full-stack journeys only)
36	└── images/ # Generated images (added separately)
37	```
38
39	For OSS deployment journeys, also create an app-specific skill:
40
41	```
42	.github/skills/<app>-azure/
43	├── SKILL.md # Overview, quick start, architecture, verification
44	├── config/
45	│ ├── environment-variables.md
46	│ └── health-probes.md
47	└── troubleshooting.md
48	```
49
50	The SKILL.md needs YAML frontmatter:
51
52	```yaml
53	---
54	name: <app>-azure
55	description: Deploy <App> to Azure. Use when deploying <App> for <purpose>.
56	---
57	```
58
59	### OSS Skill SKILL.md Structure
60
61	The skill is what the `@oss-to-azure-deployer` agent reads. Follow this section order (reference `n8n-azure` as the primary example):
62
63	1. Overview / When to Use — one paragraph
64	2. Critical: Infrastructure Generation — infrastructure is generated fresh each deployment via `azure-prepare` plugin, NOT committed to the repo
65	3. Critical: Subscription Context — read the value with `az account show --query id -o tsv`, then pass it to `azd env set AZURE_SUBSCRIPTION_ID <subscription-id>` without shell command substitution
66	4. Critical: \<App-Specific Gotcha\> — the #1 deployment failure cause (e.g., PostgreSQL SKU needs both `name` AND `tier`; Bicep outputs MUST use SCREAMING_SNAKE_CASE)
67	5. Official Documentation — link to app's docs
68	6. Quick Start (Verified) — exact prompt sequence, tested and confirmed
69	7. Key Configuration Files — table pointing to `config/environment-variables.md`, `config/health-probes.md`, `troubleshooting.md`
70	8. Architecture — Mermaid diagram of Azure resources
71	9. App-Specific Requirements — database, networking, storage, ports
72	10. Cost Estimate — table with SKUs and monthly costs
73	11. Verification Checklist — curl / az commands to confirm deployment
74	12. Tear Down — `azd down --force --purge`
75	13. Differences from Generic Patterns — what makes this app non-standard (startup timing, SSL, env vars, ports)
76
77	For AKS-based apps (like Superset), also include:
78	- `references/kubernetes-manifests.md` in the skill directory
79	- Default credentials section (e.g., admin/admin)
80	-

People who liked this also viewed

6 picks

Type