gate-check

Name: gate-check
Author: tranhieutt

69stars41forks

How to install gate-check?

tranhieutt/software_development_department/gate-check

$npx -y skills add tranhieutt/software_development_department --skill gate-check

Installs into the current project.

Summary

Validates a software product, service, or feature against readiness gates before advancing to the next delivery phase. Use when planning a phase transition or when the user mentions gate check, phase review, or readiness validation.

Files · 1

View on GitHub

SKILL.md

1	# Phase Gate Validation
2
3	This skill validates whether the software project is ready to advance to the
4	next delivery phase. It checks for required artifacts, quality standards, and
5	operational blockers.
6
7	Distinct from `/project-stage-detect`: That skill is diagnostic ("where are
8	we?"). This skill is prescriptive ("are we ready to advance?" with a formal
9	verdict).
10
11	## Production Stages (7)
12
13	The project progresses through these stages:
14
15	1. Concept - Problem framing, product concept document
16	2. Systems Design - Requirements, workflows, architecture boundaries
17	3. Technical Setup - Stack selection, CI/CD, environments, architecture decisions
18	4. Pre-Production - Spikes, prototypes, acceptance criteria, delivery planning
19	5. Production - Feature development and integration work
20	6. Polish - Stabilization, QA hardening, performance, operational readiness
21	7. Release - Go-live prep, support readiness, rollback and communication planning
22
23	When a gate passes, write the new stage name to `production/stage.txt`
24	(single line, e.g. `Production`). This updates the status line immediately.
25
26	---
27
28	## 1. Parse Arguments
29
30	- With argument: `/gate-check production` - validate readiness for that specific phase
31	- No argument: Auto-detect current stage using the same heuristics as
32	`/project-stage-detect`, then validate the NEXT phase transition
33
34	---
35
36	## 2. Phase Gate Definitions
37
38	### Gate: Concept -> Systems Design
39
40	Required Artifacts:
41	- [ ] `design/docs/product-concept.md` exists and has content
42	- [ ] Product pillars defined (in concept doc or `design/docs/product-pillars.md`)
43	- [ ] Success metrics or launch goals captured in the concept or PRD seed notes
44
45	Quality Checks:
46	- [ ] Product concept has been reviewed (`/design-review` verdict not MAJOR REVISION NEEDED)
47	- [ ] Primary user workflow or business outcome is described and understood
48	- [ ] Target audience and problem statement are identified
49
50	---
51
52	### Gate: Systems Design -> Technical Setup
53
54	Required Artifacts:
55	- [ ] Systems index exists at `design/docs/systems-index.md` with at least MVP systems enumerated
56	- [ ] At least 1 PRD in `design/docs/` (beyond product-concept.md and systems-index.md)
57
58	Quality Checks:
59	- [ ] PRD(s) pass design review (8 required sections present)
60	- [ ] System dependencies are mapped in the systems index
61	- [ ] MVP priority tier is defined
62	- [ ] Non-functional requirements are captured where relevant (performance, security, reliability, compliance)
63
64	---
65
66	### Gate: Technical Setup -> Pre-Production
67
68	Required Artifacts:
69	- [ ] Stack chosen (CLAUDE.md Technology Stack is not `[CHOOSE]`)
70	- [ ] Technical preferences configured (`.claude/docs/technical-preferences.md` populated)
71	- [ ] At least 1 Architecture Decision Record in `docs/architecture/`
72	- [ ] CI/CD workflow, build script, or release automation exists
73	- [ ] Environment strategy documented (dev/staging/prod, secrets handling, deployment path)
74
75	Quality Checks:
76	- [ ] Architecture decisions cover core domains, data flow, integrations, and deployment concerns
77	- [ ] Technical preferences have naming conventions and performance budgets set
78	- [ ] Operational ownership is clear for build, deploy, and rollback paths
79
80	---
81
82	### Gate: Pre-Production -> Production
83
84	Required Artifacts:
85	- [ ] At least 1 prototype, spike, or technical validation artifact exists with notes or a README
86	- [ ] First sprint plan exists in `production/sprints/`
87	- [ ] All MVP-tier PRDs from systems index are complete
88	- [ ] Initial delivery scope is defined for the first release or milestone
89
90	Quality Checks:
91	- [ ] Prototype or spike validates the riskiest technical assumption or critical user workflow
92	- [ ] Sprint plan references real work items from PRDs
93	- [ ] Acceptance criteria and release scope are defined
94	- [ ] Dependencies and sequencing risks are identified
95
96	---
97
98	### Gate: Production -> Polish
99
100	Required Artifacts:
101	- [ ] `src/` has active code organized into subsystems
102	- [ ] All core workflows from PRD are implemented (cross-reference `design/docs/` with `src/`)
103	- [ ] Main user journey works end-to-end in a dev or staging environment
104	- [ ] Test files exist in `tests/`
105	- [ ] Deployment or release scripts exist
106	- [ ] QA/UAT evidence exists (test summary, checklist, sign-off notes, or release candidate results)
107
108	Quality Checks:
109	- [ ] Tests are passing (run test suite via `Bash`)
110	- [ ] No cri

People who liked this also viewed

6 picks

Type

gate-check

69stars41forks

View on GitHub

How to install gate-check?

tranhieutt/software_development_department/gate-check

$npx -y skills add tranhieutt/software_development_department --skill gate-check

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Phase Gate Validation
2
3	This skill validates whether the software project is ready to advance to the
4	next delivery phase. It checks for required artifacts, quality standards, and
5	operational blockers.
6
7	Distinct from `/project-stage-detect`: That skill is diagnostic ("where are
8	we?"). This skill is prescriptive ("are we ready to advance?" with a formal
9	verdict).
10
11	## Production Stages (7)
12
13	The project progresses through these stages:
14
15	1. Concept - Problem framing, product concept document
16	2. Systems Design - Requirements, workflows, architecture boundaries
17	3. Technical Setup - Stack selection, CI/CD, environments, architecture decisions
18	4. Pre-Production - Spikes, prototypes, acceptance criteria, delivery planning
19	5. Production - Feature development and integration work
20	6. Polish - Stabilization, QA hardening, performance, operational readiness
21	7. Release - Go-live prep, support readiness, rollback and communication planning
22
23	When a gate passes, write the new stage name to `production/stage.txt`
24	(single line, e.g. `Production`). This updates the status line immediately.
25
26	---
27
28	## 1. Parse Arguments
29
30	- With argument: `/gate-check production` - validate readiness for that specific phase
31	- No argument: Auto-detect current stage using the same heuristics as
32	`/project-stage-detect`, then validate the NEXT phase transition
33
34	---
35
36	## 2. Phase Gate Definitions
37
38	### Gate: Concept -> Systems Design
39
40	Required Artifacts:
41	- [ ] `design/docs/product-concept.md` exists and has content
42	- [ ] Product pillars defined (in concept doc or `design/docs/product-pillars.md`)
43	- [ ] Success metrics or launch goals captured in the concept or PRD seed notes
44
45	Quality Checks:
46	- [ ] Product concept has been reviewed (`/design-review` verdict not MAJOR REVISION NEEDED)
47	- [ ] Primary user workflow or business outcome is described and understood
48	- [ ] Target audience and problem statement are identified
49
50	---
51
52	### Gate: Systems Design -> Technical Setup
53
54	Required Artifacts:
55	- [ ] Systems index exists at `design/docs/systems-index.md` with at least MVP systems enumerated
56	- [ ] At least 1 PRD in `design/docs/` (beyond product-concept.md and systems-index.md)
57
58	Quality Checks:
59	- [ ] PRD(s) pass design review (8 required sections present)
60	- [ ] System dependencies are mapped in the systems index
61	- [ ] MVP priority tier is defined
62	- [ ] Non-functional requirements are captured where relevant (performance, security, reliability, compliance)
63
64	---
65
66	### Gate: Technical Setup -> Pre-Production
67
68	Required Artifacts:
69	- [ ] Stack chosen (CLAUDE.md Technology Stack is not `[CHOOSE]`)
70	- [ ] Technical preferences configured (`.claude/docs/technical-preferences.md` populated)
71	- [ ] At least 1 Architecture Decision Record in `docs/architecture/`
72	- [ ] CI/CD workflow, build script, or release automation exists
73	- [ ] Environment strategy documented (dev/staging/prod, secrets handling, deployment path)
74
75	Quality Checks:
76	- [ ] Architecture decisions cover core domains, data flow, integrations, and deployment concerns
77	- [ ] Technical preferences have naming conventions and performance budgets set
78	- [ ] Operational ownership is clear for build, deploy, and rollback paths
79
80	---
81
82	### Gate: Pre-Production -> Production
83
84	Required Artifacts:
85	- [ ] At least 1 prototype, spike, or technical validation artifact exists with notes or a README
86	- [ ] First sprint plan exists in `production/sprints/`
87	- [ ] All MVP-tier PRDs from systems index are complete
88	- [ ] Initial delivery scope is defined for the first release or milestone
89
90	Quality Checks:
91	- [ ] Prototype or spike validates the riskiest technical assumption or critical user workflow
92	- [ ] Sprint plan references real work items from PRDs
93	- [ ] Acceptance criteria and release scope are defined
94	- [ ] Dependencies and sequencing risks are identified
95
96	---
97
98	### Gate: Production -> Polish
99
100	Required Artifacts:
101	- [ ] `src/` has active code organized into subsystems
102	- [ ] All core workflows from PRD are implemented (cross-reference `design/docs/` with `src/`)
103	- [ ] Main user journey works end-to-end in a dev or staging environment
104	- [ ] Test files exist in `tests/`
105	- [ ] Deployment or release scripts exist
106	- [ ] QA/UAT evidence exists (test summary, checklist, sign-off notes, or release candidate results)
107
108	Quality Checks:
109	- [ ] Tests are passing (run test suite via `Bash`)
110	- [ ] No cri

People who liked this also viewed

6 picks

Type