geo-software-product-grilling SKILL.md skillA

geo-software-product-grilling from yuiseki/geo-software-factory is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add yuiseki/geo-software-factory/geo-software-product-grilling@git:20261113.0d9593d

Pins git:20261113.0d9593d in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
yuiseki/geo-software-factory
Path
.agents/skills/geo-software-product-grilling/SKILL.md
Versions recorded
5
Latest version
git:20261113.0d9593d, committed Nov 13, 2026
First version recorded
Nov 12, 2026
Size
9,317 bytes
Repository stars
12
License
Apache-2.0

作りたい地図プロダクトについて、誰にどんな価値を届けたいのか、その価値のためにどの機能を実装すべきかが十分に明確になるまで、選択肢で答えられる質問を 1 問ずつ重ねて問い詰める。「地図アプリを作りたい」「地図サービスを企画している」「地図を使って何かしたい」のように目的や要件が曖昧な依頼、または技術選定を頼まれたが要件が聞き出せていないときに使う。.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# geo-software-product-grilling

作りたい地図プロダクトを、本人への選択肢つきの質問を 1 問ずつ重ねて明確にし、プロダクト概要にまとめる。本人の頭の中の答えを当てにいくのではなく、エージェントが材料から選択肢を作り、本人が選ぶか書き換えることで、2 人で概要を形にしていく。

| reference | 読むとき | 中身 |
|---|---|---|
| [question-bank](references/question-bank.md) | 質問を組み立てるとき | 観点ごとの質問と選択肢の作り方、2026-11-10 の聞き取りの実例 |
| [enterprise-contract](references/enterprise-contract.md) | 業務用・受託・自治体案件のとき | 検収条件、納入物、既存台帳連携、閉域網、SLA、アクセシビリティの追加質問 |

ひな形は [assets/product-brief-template.md](assets/product-brief-template.md)。夜に渡す前に [scripts/check_brief.py](scripts/check_brief.py) で、価値の芯、Must、シナリオの置き場所、判断の方針が埋まり、「準備したもの」の鍵の名前が設定済みで CLI があるかを確かめる (値は読まない)。

## 目的

次がそろったら問い詰めを終え、プロダクト概要にまとめて確認をとる。

- 一行の説明: 誰の、どんな困りごとを、地図で何をすることで解くか
- 価値の順位: 届ける価値を、本人が重要な順に並べたもの (最重要、重要、副次的)
- 機能: Must / Should / Could。最初の版の期限があれば、その期限までの Must
- 後の段階の入口の条件 (リポジトリ直下の AGENTS.md の表): geo-software-arch の 4 項目 (要る機能、データの大きさと対象範囲、ルールの強制、対象端末) と、geo-software-infra の 3 項目 (利用形態、規模、対象地域)。分からない項目は「未定」と書けるが、推測では埋めない

## 進め方

1. 依頼と、本人が示した材料 (参考の URL、過去の記録、似たサービス) を読む。材料は質問と選択肢を作るためだけに使い、読んだ結果の要約や、エージェントの見立てを本人に先に見せない。見せると、本人が自分の答えではなく見立てに寄せてしまう
2. 1 回に 1 問だけ聞く。質問の頭に「N 問目です」と番号を付ける
…

Read the whole file at its exact version.

How to install

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_mbsnjfz52y37enmq/fa013651191010f5531a466b992e8a576b4beb34f26c590555dfb3ea8fbdd93c.json

Then /plugin install geo-software-product-grilling@markdownregistry-mbsnjfz52y37enmq in Claude Code. It installs git:20261113.0d9593d, the one graded A here, pinned to the commit it was graded at, and leaves it there.

The exact contents, by fingerprint
mdr add yuiseki/geo-software-factory/geo-software-product-grilling@sha256:fa013651191010f5

The line at the top of this page pins the label git:20261113.0d9593d, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_mbsnjfz52y37enmq.svg)](https://markdownregistry.com/a/art_mbsnjfz52y37enmq)

1 badge image fetches in 30 days. What the badge shows.

Ask from your agent
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry

Then ask it: what changed in yuiseki/geo-software-factory/geo-software-product-grilling since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.

Got a copy of geo-software-product-grilling from somewhere else? Ask it: where did my geo-software-product-grilling come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.

Versions

The registry has recorded 5 versions of this file, between Nov 12, 2026 and Nov 13, 2026, more than one a day.

Watch this file (sign in, one email per new version)

versioncommittedcommitsizeaudit
git:20261113.0d9593d latest2026-11-13 0d9593d 9,317 BA view · diff
git:20261112.e30bb8e2026-11-12 e30bb8e 9,100 BA view · diff
git:20261112.df5079c2026-11-12 df5079c 8,831 BA view · diff
git:20261112.b377d972026-11-12 b377d97 8,324 BA view · diff
git:20261112.c0781402026-11-12 c078140 8,221 BA view
Keep it current by itself, install once

Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

Install on GitHub

It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.

Keep it current by itself

Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml

It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.

Check a whole project

From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies

In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies

No sha256sum on your machine? shasum -a 256 prints the same lines.

Audit of the latest version

A  17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • pass: Frontmatter block present
  • pass: Frontmatter declares a name
  • pass: Frontmatter declares a description
  • pass: Size between 200 bytes and 200 KB (9317 bytes)
  • pass: No zero-width or bidi control characters
  • pass: No instruction hidden inside an HTML comment
  • pass: No link to an exfiltration or paste host
  • pass: No credential-shaped string
  • pass: No instruction to send local credentials anywhere
  • pass: No text hidden with inline styles
  • pass: No prompt-injection phrasing
  • pass: No curl or wget piped into a shell
  • pass: No recursive delete of root, home or parent
  • pass: No instruction to read or print local credentials
  • pass: No base64 blob over 200 characters
  • pass: No link to a raw IP address
  • pass: No script tag

Source

GitHub

yuiseki/geo-software-factory · 12 stars · license Apache-2.0 · pushed 2026-11-16 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_mbsnjfz52y37enmq
GET https://markdownregistry.com/api/v1/resolve?ref=yuiseki/geo-software-factory/geo-software-product-grilling
GET https://markdownregistry.com/api/v1/blob/fa013651191010f5531a466b992e8a576b4beb34f26c590555dfb3ea8fbdd93c

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from yuiseki/geo-software-factory

AGENTS.md@.agents/skills AGENTS.md file
yuiseki/geo-software-factory · .agents/skills/AGENTS.md
git:20261113.a912aab · audit A · 12 stars
geo-software-arch SKILL.md skill
yuiseki/geo-software-factory · .agents/skills/geo-software-arch/SKILL.md · 地図プロダクトのアーキテクチャを、保存・計算・表現の 3 つの要素と、クラウド・エッジ・ブラウザ/アプリの 3 つの置き場所の組み合わせとして比較し決める。タイル配信、検索…
git:20261113.2f9f217 · audit A · 12 stars
geo-software-auth SKILL.md skill
yuiseki/geo-software-factory · .agents/skills/geo-software-auth/SKILL.md · 地図プロダクトの認証と認可の仕組みを比較し選ぶ。管理型の認証サービス (Auth0、Clerk、Firebase Authentication、Supabase Auth、Neon Auth、Amazon…
git:20261112.c078140 · audit A · 12 stars
geo-software-build SKILL.md skill
yuiseki/geo-software-factory · .agents/skills/geo-software-build/SKILL.md · 技術選定の済んだ地図プロダクトを、人間を呼ばずに実装してテストし、実装と別の評価者 (geo-software-eval) の評価に通るまで直す。技術選定の結果から、テストを先に書いて小さく積み、地図に載せるデータを出典つきで組み立て、画面…
git:20261114.05b9cc4 · audit A · 12 stars
geo-software-data SKILL.md skill
yuiseki/geo-software-factory · .agents/skills/geo-software-data/SKILL.md · 地図に載せる主題データ (ベースマップ以外) の出どころを比較し選ぶ。OpenStreetMap、Overture Maps、国土数値情報、基盤地図情報、e-Stat…
git:20261113.0d9593d · audit A · 12 stars
geo-software-deploy SKILL.md skill
yuiseki/geo-software-factory · .agents/skills/geo-software-deploy/SKILL.md · 実装とテストの済んだ地図プロダクトを、人間を呼ばずに公開し、本番で確かめる。昼に準備した認証と権限の範囲で、DB のマイグレーション、デプロイ、独自ドメインの割り当て、本番の URL…
git:20261113.0d9593d · audit A · 12 stars
geo-software-eval SKILL.md skill
yuiseki/geo-software-factory · .agents/skills/geo-software-eval/SKILL.md · 地図プロダクトの正しさを、人間のコードレビューに頼らずに評価する仕組み (評価ハーネス) を設計し、動かす。昼に人間と一緒に、利用者が達成したいことを外から観測できるシナリオにし、実装から切り離して置く。夜は実装とは別の評価者がシナリオを手…
git:20261114.7ec3565 · audit A · 12 stars
geo-software-growth SKILL.md skill
yuiseki/geo-software-factory · .agents/skills/geo-software-growth/SKILL.md · (未着手のプレースホルダー。中身はまだ無い) 公開した地図アプリの利用者を増やす。手順が書かれるまでは使わない。
git:20261112.c078140 · audit A · 12 stars
geo-software-infra SKILL.md skill
yuiseki/geo-software-factory · .agents/skills/geo-software-infra/SKILL.md · 地図プロダクトの要件に応じて、ベースマップ、衛星・航空写真、3D データの供給元を比較し技術選定する。商用サービス (Google Maps, Mapbox, MapTiler, Esri, HERE, TomTom, Geolonia…
git:20261116.e26f846 · audit A · 12 stars
geo-software-legal-check SKILL.md skill
yuiseki/geo-software-factory · .agents/skills/geo-software-legal-check/SKILL.md · 地図プロダクトを公開する前に、法令と規約と権利の確認をする。帰属表示、ODbL の派生データベース、測量法による地図の複製・使用の承認 (地理院地図、基盤地図情報)、位置情報と個人情報、電気通信事業法の外部送信規律、地図 API の規約…
git:20261112.c078140 · audit A · 12 stars
geo-software-library SKILL.md skill
yuiseki/geo-software-factory · .agents/skills/geo-software-library/SKILL.md · 地図プロダクトを実装するためのライブラリや SDK を、要件に応じて比較し技術選定する。Web (Leaflet, MapLibre GL JS, Mapbox GL JS, Google Maps JavaScript API…
git:20261116.e26f846 · audit A · 12 stars
geo-software-migrate SKILL.md skill
yuiseki/geo-software-factory · .agents/skills/geo-software-migrate/SKILL.md · 既存の地図プロダクトを、別の地図サービスやライブラリへ乗り換える計画を立てる。Google Maps Platform、Mapbox、Leaflet とラスタタイルからの移行で、今の地図が使っているものの棚卸し、API…
git:20261114.05b9cc4 · audit A · 12 stars

Every file in yuiseki/geo-software-factory

Browse by kind, by grade A, or by owner.

Kept in .agents/skills, the folder Codex reads. More agent skills for Codex.