菜单
Harvest ponytail: comment markers into a debt ledger. Use for "ponytail debt", "/ponytail-debt", "list shortcuts", "ponytail ledger". Read-only unless user asks to write PONYTAIL-DEBT.md.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | ponytail-debt |
| description | Harvest ponytail: comment markers into a debt ledger. Use for "ponytail debt", "/ponytail-debt", "list shortcuts", "ponytail ledger". Read-only unless user asks to write PONYTAIL-DEBT.md. |
On-demand loading: Read when tracking deliberate ponytail deferrals marked in code.
Adapted from ponytail-debt (MIT). Works with rules/overlay-ponytail.mdc ponytail: convention.
Grep repo for comment markers (skip node_modules, .git, build output):
rg -n "ponytail:" --glob "!node_modules/**" --glob "!.git/**"
Each hit = one ledger row. Convention: ponytail: <ceiling>, <upgrade trigger>.
Output grouped by file:
path:line — ceiling: … upgrade: …
Tag no-trigger when no upgrade path is named (rot risk).
End with N markers, M with no trigger. or No ponytail: debt. Clean ledger.
Read-only by default. Persist to PONYTAIL-DEBT.md only when user asks.
Orchestrate continual learning by delegating transcript mining and AGENTS.md updates to the knowledge-synthesizer subagent. Use when asked to mine prior chats, maintain AGENTS.md, update learned preferences, or run the continual-learning loop.
Security-focused review of code diffs and PRs with surface classification and Semgrep on changed files. Use when reviewing pull requests, branch diffs, or validating security regressions before merge.
Live Notion session log (L4b) — create, incremental updates during work, finalize on CLOSE. Works on any Cursor project workspace.
Bootstrap a new project with Cursor-ready configuration: AGENTS.md, per-project .cursor/rules/project-conventions.mdc, and optional memory_bank/ scaffold. Use at project initialization, when starting a new repo, or when the user says "set up Cursor for this project" / "bootstrap this project" / "init project config".
Phase-1 repo reconnaissance as a standalone skill: stack detection, relevant files, validation commands from repo evidence, workflow hints, and risk flags. Use inside /scout, /ks-conductor pre-flight, or any read-only discovery before planning or implementation.
Validates phase outputs before advancing the SDLC. Defines expected artifacts per phase (intake, scout, plan, critic, build, test, review, document, close) and produces a clear PASS / CONDITIONAL / BLOCK verdict with gaps. Use at orchestrator or command phase boundaries, before expensive work, or when the user asks to verify a gate or "are we ready to proceed".
