メニュー
[Workflow] Use when activating the Greenfield Project Init workflow for full waterfall project inception from idea through implementation with integration testing.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/duc01226/EasyPlatform --skill workflow-greenfield-initコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
[Architecture] Use when designing solution architecture across backend, frontend, deployment, monitoring, testing, and code quality.
[Utilities] Use when you need to answer technical and architectural questions.
[Content] Use when you need to brainstorm as a PO/BA — structured ideation for problem-solving, new product creation, or feature enhancement.
SOC 職業分類に基づく
| name | workflow-greenfield-init |
| version | 1.0.0 |
| description | [Workflow] Use when activating the Greenfield Project Init workflow for full waterfall project inception from idea through implementation with integration testing. |
| disable-model-invocation | false |
Goal: [Workflow] Trigger Greenfield Project Init workflow — full waterfall project inception from idea through implementation with integration testing.
Workflow:
Key Rules:
file:line) with confidence >80% to act.Business Intent / Invariant Guarded or the protected business intent/invariant and ensure the test would fail if that intent breaks.This workflow has steps that appear multiple times. When creating tasks, use these descriptions to distinguish them:
| Step | Occurrence | Task Description |
|---|---|---|
/plan | 1st (pos 11) | PLAN₁: High-level architecture plan (after architecture-design) |
/plan | 2nd (pos 31) | PLAN₂: Sprint-ready implementation plan (after review-artifact --type=spec-tests) |
/plan | 3rd (pos 42) | PLAN₃: Integration test architecture plan (post-implementation) |
/plan-review | 1st (pos 12) | Review PLAN₁ architecture (immediate gate; replaces former rationale why-review) |
/plan-review | 2nd (pos 15) | Re-review PLAN₁ after architecture-security + performance analysis |
/plan-review | 3rd (pos 32) | Review PLAN₂ implementation |
/plan-review | 4th (pos 43) | Review PLAN₃ integration tests |
/security-review | 1st (pos 13) | Architecture security review |
/security-review | 2nd (pos 50) | Production readiness security review |
/spec [mode=tests] | 1st (pos 27) | TDD-SPEC₁: Feature test specs (before implementation) |
/spec [mode=tests] | 2nd (pos 39) | TDD-SPEC₂: Post-implementation test spec update |
/review-artifact --type=spec-tests | 1st (pos 29) | Review TDD-SPEC₁ |
/review-artifact --type=spec-tests | 2nd (pos 41) | Review TDD-SPEC₂ |
/test | 1st (pos 47) | Test after integration tests |
/test | 2nd (pos 52) | Final test verification |
/review-domain-entities | 1st (pos 38) | DDD quality review — conditional: skip if no domain entity files in changeset |
/linter-setup | (new) | LINTER-SETUP: Install and configure computational feedback sensors |
/harness-setup | (new) | HARNESS-SETUP: Full outer agent harness (feedforward guides + feedback sensors inventory) |
NEVER deduplicate — each occurrence is a distinct task with a different purpose.
IMPORTANT MANDATORY Steps: /idea -> /web-research -> /deep-research -> /business-evaluation -> /spec-discovery -> /domain-analysis -> /why-review -> /tech-stack-research -> /architecture-design -> /why-review -> /plan -> /plan-review -> /security-review -> /performance-review -> /plan-review -> /refine -> /why-review -> /review-artifact --type=pbi -> /story -> /why-review -> /review-artifact --type=story -> /pbi-challenge -> /dor-gate -> /pbi-mockup -> /plan-validate -> /why-review -> /spec [mode=tests] -> /why-review -> /review-artifact --type=spec-tests -> /spec-clarify -> /plan -> /plan-review -> /scaffold -> /linter-setup -> /harness-setup -> /why-review -> /plan-execute -> /review-domain-entities -> /spec [mode=tests] -> /why-review -> /review-artifact --type=spec-tests -> /plan -> /plan-review -> /integration-test -> /integration-test-review -> /integration-test-verify -> /test -> /workflow-review-changes -> /production-readiness-review -> /security-review -> /changelog -> /test -> /docs-update -> /workflow-end -> /watzup
IMPORTANT MANDATORY Steps: /idea -> /web-research -> /deep-research -> /business-evaluation -> /spec-discovery -> /domain-analysis -> /why-review -> /tech-stack-research -> /architecture-design -> /why-review -> /plan -> /plan-review -> /security-review -> /performance-review -> /plan-review -> /refine -> /why-review -> /review-artifact --type=pbi -> /story -> /why-review -> /review-artifact --type=story -> /pbi-challenge -> /dor-gate -> /pbi-mockup -> /plan-validate -> /why-review -> /spec [mode=tests] -> /why-review -> /review-artifact --type=spec-tests -> /spec-clarify -> /plan -> /plan-review -> /scaffold -> /linter-setup -> /harness-setup -> /why-review -> /plan-execute -> /review-domain-entities -> /spec [mode=tests] -> /why-review -> /review-artifact --type=spec-tests -> /plan -> /plan-review -> /integration-test -> /integration-test-review -> /integration-test-verify -> /test -> /workflow-review-changes -> /production-readiness-review -> /security-review -> /changelog -> /test -> /docs-update -> /workflow-end -> /watzup
[BLOCKING] Each step MUST ATTENTION invoke its
Skilltool — marking a taskcompletedwithout skill invocation is a workflow violation. NEVER batch-complete validation gates.
Activate the workflow-greenfield-init workflow. Run /start-workflow workflow-greenfield-init with the user's prompt as context.
Steps: /idea → /web-research → /deep-research → /business-evaluation → /spec-discovery → /domain-analysis → /why-review → /tech-stack-research → /architecture-design → /why-review → /plan → /plan-review → /security-review → /performance-review → /plan-review → /refine → /why-review → /review-artifact --type=pbi → /story → /why-review → /review-artifact --type=story → /pbi-challenge → /dor-gate → /pbi-mockup → /plan-validate → /why-review → /spec [mode=tests] → /why-review → /review-artifact --type=spec-tests → /spec-clarify → /plan → /plan-review → /scaffold → /linter-setup → /harness-setup → /why-review → /plan-execute → /review-domain-entities → /spec [mode=tests] → /why-review → /review-artifact --type=spec-tests → /plan → /plan-review → /integration-test → /integration-test-review → /integration-test-verify → /test → /workflow-review-changes → /production-readiness-review → /security-review → /changelog → /test → /docs-update → /workflow-end → /watzup
Lean variant (
mode=lean) — for low-risk or solo greenfield inception, a trimmed path is available (formerly a separate lean greenfield wrapper, now merged here). It keeps the same backbone but drops the per-step/why-reviewrationale gates (retaining only the single pre-/plan-execute/why-review),/pbi-challenge,/dor-gate, and the/integration-test-review+/integration-test-verifygates. Use ONLY when inception risk is low; default to the full rigorous sequence above. The authoritative sequence is theworkflow-greenfield-initentry inworkflows.json— the lean path is a documented gate-skip option, not a separate workflow.
AI Mistake Prevention — Failure modes to avoid on every task:
Re-read files after context changes. Context compaction, resume, or long-running work can make memory stale; verify current files before acting. Verify generated content against source evidence. AI hallucinates APIs, names, claims, and document facts. Check the relevant source before documenting or referencing. Check downstream references before deleting or renaming. Removing an artifact can stale docs, generated mirrors, configs, and callers; map references first. Trace the full impact chain after edits. Changing a definition can miss derived outputs and consumers. Follow the affected chain before declaring done. Verify ALL affected outputs, not just the first. One green check is not all green checks; validate every output surface the change can affect. Assume existing values are intentional — ask WHY before changing. Before changing a constant, limit, flag, wording, or pattern, read nearby context and history. Surface ambiguity before acting — don't pick silently. Multiple valid interpretations require an explicit question or stated assumption with risk. Keep shared guidance role-relevant. Universal guidance must help every receiving skill or agent; code-specific obligations belong only in code-specific protocols.
Nested Task Expansion Contract — For workflow-step invocation, the
[Workflow] ...row is only a parent container; the child skill still creates visible phase tasks.
- Call
TaskListfirst. If a matching active parent workflow row exists, setnested=trueand recordparentTaskId; otherwise run standalone.- Create one task per declared phase before phase work. When nested, prefix subjects
[N.M] $skill-name — phase.- When nested, link the parent with
TaskUpdate(parentTaskId, addBlockedBy: [childIds]).- Orchestrators must pre-expand a child skill's phase list and link the workflow row before invoking that child skill or sub-agent.
- Mark exactly one child
in_progressbefore work andcompletedimmediately after evidence is written.- Complete the parent only after all child tasks are completed or explicitly cancelled with reason.
Blocked until:
TaskListdone, child phases created, parent linked when nested, first child markedin_progress.
Critical Thinking Mindset — Apply critical thinking, sequential thinking. Every claim needs traced proof, confidence >80% to act. Anti-hallucination: Never present guess as fact — cite sources for every claim, admit uncertainty freely, self-check output for errors, cross-reference independently, stay skeptical of own confidence — certainty without evidence root of all hallucination.
Incremental Result Persistence — MANDATORY for all sub-agents or heavy inline steps processing >3 files.
- Before starting: Create report file
plans/reports/{skill}-{date}-{slug}.md- After each file/section reviewed: Append findings to report immediately — never hold in memory
- Return to main agent: Summary only (per SYNC:subagent-return-contract) with
Full report:path- Main agent: Reads report file only when resolving specific blockers
Why: Context cutoff mid-execution loses ALL in-memory findings. Each disk write survives compaction. Partial results are better than no results.
Report naming:
plans/reports/{skill-name}-{YYMMDD}-{HHmm}-{slug}.md
Sub-Agent Return Contract — When this skill spawns a sub-agent, the sub-agent MUST return ONLY this structure. Main agent reads only this summary — NEVER requests full sub-agent output inline.
## Sub-Agent Result: [skill-name] Status: ✅ PASS | ⚠️ PARTIAL | ❌ FAIL Confidence: [0-100]% ### Findings (Critical/High only — max 10 bullets) - [severity] [file:line] [finding] ### Actions Taken - [file changed] [what changed] ### Blockers (if any) - [blocker description] Full report: plans/reports/[skill-name]-[date]-[slug].mdMain agent reads
Full reportfile ONLY when: (a) resolving a specific blocker, or (b) building a fix plan. Sub-agent writes full report incrementally (per SYNC:incremental-persistence) — not held in memory.Context budget — the return payload is a SUMMARY, not a transcript: ≤10 finding bullets, no raw file contents / full diffs / verbatim logs inline, no re-pasted source. Everything beyond the summary lives in the
Full reporton disk. A sub-agent that would exceed the summary shape MUST write the detail to its report and return only the pointer — the orchestrator's context is the scarce resource the whole map-reduce protects.
MUST ATTENTION apply critical + sequential thinking — every claim needs appropriate traced evidence (file:line for repo/code claims; source URL or artifact section for research, product, content, and docs claims); confidence >80% to act, <60% DO NOT recommend. Anti-hallucination: never present guess as fact, admit uncertainty freely, cross-reference independently, stay skeptical of own confidence.
MUST ATTENTION apply AI mistake prevention — verify generated content against evidence, trace downstream references before deleting or renaming, verify all affected outputs, re-read files after context loss, and surface ambiguity before acting.
[N.M] $skill-name — phase prefixes and one-in_progress discipline.Protocols in force (concise digest of the SYNC/shared blocks this skill carries):
in_progress.file:line proof per claim, confidence >80% to act.plans/reports/ per file, never hold in memory.IMPORTANT MUST ATTENTION break work into small todo tasks using TaskCreate BEFORE starting
IMPORTANT MUST ATTENTION search codebase for 3+ similar patterns before creating new code
IMPORTANT MUST ATTENTION cite file:line evidence for every claim (confidence >80% to act)
IMPORTANT MUST ATTENTION add a final review todo task to verify work quality
[TASK-PLANNING] Before acting, analyze task scope and systematically break it into small todo tasks and sub-tasks using TaskCreate.
[IMPORTANT] Analyze how big the task is and break it into many small todo tasks systematically before starting — this is very important.