- name
SKILL.md
스킬 파일은 게시자의 저장소에 그대로 있습니다.
복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add phuryn/product-engineering --skill document-app -a cursor -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add phuryn/product-engineering --skill document-app -a claude-code -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add phuryn/product-engineering --skill document-app -a codex -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add phuryn/product-engineering --skill document-app -a grok -y복사한 메시지를 Grok Bot 채팅에 보냅니다. Bot이 GitHub에서 이 SKILL.md를 가져와 모든 Bot이 공유하는 스킬에 추가합니다.
Install this skill: https://github.com/phuryn/product-engineering/tree/HEAD/ai-shipping/skills/document-app게시자 제공
Document the system honestly so people and agents can review it. Produce the durable documentation an AI-built app is missing. Map what the system is, who can do what, and where the risk lives. These docs are the foundation every later audit compares the code against.
Use check-only mode when asked only to check the docs. A request that starts with check also selects that mode, on the scope that follows it.
/ai-shipping:document-app Claude Code
/ai-shipping:document-app supabase/functions
$ai-shipping:document-app the backend Codex
/ai-shipping:document-app check
"document this app" · "check our docs against the code" either agent, in plain words
Document the requested scope, or the whole repository when none is given. If the request starts with check, skip to Check-only mode with the rest as the scope. For the whole repository, prioritize backend code, auth, data access, background jobs, and anything that sends, schedules, or exposes data.
Read the code as the source of truth for system docs. Apply the shipping-artifacts skill and produce the applicable documents. Follow its Locations and names rule: use the repo's own docs location and existing equivalents first. Use the names below, in documentation/ at the repo root, only where the repo has none.
For large scopes, give parallel subagents one core document each. Each reads the code slice its doc describes; reconcile the cross-references yourself.
Always produce the core documents. They cover:
architecture.md — system overview, stack, auth flow, trust boundaries.flows.md — the permission-relevant journeys: each protected step's authz check, the trust-boundary crossings, and the side effects each flow causes.permissions.md — roles, scope derivation, resource × operation × role matrix, RLS vs. code-enforced checks.variables.md — config & secrets mapped to risk and rotation.Produce a conditional document only when its capability exists. Otherwise, note its absence in one line rather than inventing content.
emails.md — notification path, templates, retry/backoff, failure visibility.cron.md — scheduled-work inventory, idempotency, internal-call auth.seo.md — SPA preview approach, route coverage, metadata sanitization.automation.md — embedded agents/automations: trigger, tool surface, steering vs. hard guardrails, output contract, app-owned side effects, approval gates.Describe the current state honestly, without being paranoid. Skip conditional documents that do not apply and say so. Add a "Related Documents" reference in architecture.md for each doc produced. The test-coverage map, tests.md, is produced separately by the derive-tests skill.
Report every document's path, what was skipped, and what remains unclear. Say what was created or updated and whether each path follows the repo's setup or a plugin default. Explain each skip and any gaps where the code was too unclear to document confidently; those are the first things to fix.
Offer the next steps after reporting the documentation work. Use these options:
derive-tests skill) so each documented rule has a verification plan?"/ai-shipping:ship-check, or $ai-shipping:ship-check in Codex) to wire agent context and produce a full shipping packet?"Check-only mode reports disagreements and writes no file. This lets a release check hand-maintained intent against code without overwriting it. Write no doc, report, or draft of a missing doc.
intended-vs-implemented skill's discipline: cite both the claim and its code path. Report every factual disagreement, not only the ones that cross a boundary; skip wording and style.Print the output in the conversation:
Doc check: [scope] — check-only, no files written
### Disagreements
1. [topic]
- Doc says: [claim] — `[doc path]:[line]`
- Code does: [behavior] — `[code path]:[line]`
- Owner decides: fix the code or fix the doc.
### In the code, in no doc
- [behavior] — `[code path]:[line]` (would belong in [doc])
### Not checked
- [absent docs, claims too vague to verify, code out of scope]
### Summary
Doc check, [date], commit [short SHA], scope [scope]: [N] docs read, [N] disagreements, [N] undocumented behaviors, [N] not checked. No files written. Which side to fix is the owner's call.
State what was read when the Disagreements section is empty. Then stop: don't offer to rewrite the docs.
AGENTS.md or CLAUDE.md, whichever the repo's structure makes canonical. It contains instructions derived from these docs.Every core doc exists or is listed as absent with the reason. Each claim points to its code, and the report names unclear-code gaps; in check mode, nothing on disk changed.
'Document the app': write or refresh an app's system docs from its code. 'Are the docs right?': check mode, which only reports where docs and code disagree.
---name: document-appdescription: 'Document the app': write or refresh an app's system docs from its code. 'Are the docs right?': check mode…---# ai-shipping/skills/document-app/SKILL.mdFAQ
게시자에게서 ai-shipping/skills/document-app/SKILL.md를 다운로드하거나 경로를 복사해 저장소를 엽니다. PlugMCP는 스킬을 목록에 올릴 뿐 파일을 호스팅하지 않습니다.
게시자가 https://github.com/phuryn/product-engineering에서 관리합니다.
Claude, Cursor, Codex, Grok Build는 게시자의 저장소에서 추가한 SKILL.md를 읽을 수 있습니다. Grok Bot은 채팅에서 스킬의 GitHub 폴더 링크를 보내면 설치합니다.