AGENT SKILL

pp-progress

Use when checking specification progress, review scores, translation sync status, or determining the next pipeline step.

License 许可
MIT
最近更新
2026-11-11
Stars
★ 2
Forks
0

01 前言 Front Matter

name
pp-progress
description
Use when checking specification progress, review scores, translation sync status, or determining the next pipeline step.
allowed-tools
Read, Glob, Grep
argument-hint
[feature-name]
user-invocable
true

03 SKILL.md 正文

Specification Status

Show status for: $ARGUMENTS

Instructions

Step 0: Read Configuration

  1. Read .claude/planning-plugin.json from the current project directory
  2. If the file does not exist, stop with a guidance message:

    "Planning Plugin is not configured for this project. Run /planning-plugin:pp-init to set up."

  3. Extract workingLanguage (default: "en" if field is absent)
  4. Extract supportedLanguages (default: ["en", "ko", "vi"])
  5. Language name mapping: en = English, ko = Korean, vi = Vietnamese

Communication language: All user-facing output in this skill (summaries, questions, feedback presentations, next-step guidance) must be in {workingLanguage_name}.

If a feature name is provided:

  1. Read the progress file at docs/specs/{feature}/.progress/{feature}.json
  2. If the progress file contains workingLanguage, use that value (ignore planning-plugin.json for existing specs)
  3. Determine target languages: supportedLanguages minus the spec's workingLanguage
  4. Display:
Feature: {feature}
Status: {status}
Working Language: {workingLanguage_name}
Current Round: {currentRound} (if reviewCycleStart > 0, append: " — cycle started at round {reviewCycleStart + 1}")

Review History:
┌───────┬─────────────────┬──────────────────┬──────────────────┐
│ Round │ Planner Score   │ Tester Score     │ Key Decisions    │
├───────┼─────────────────┼──────────────────┼──────────────────┤
│   1   │ {score}/10      │ {score}/10       │ {decisions}      │
└───────┴─────────────────┴──────────────────┴──────────────────┘

Translation Status:
  {target_lang_1_name} ({target_lang_1}):  {synced ? "Synced" : "Out of sync"} — Last synced: {timestamp}
  {target_lang_2_name} ({target_lang_2}):  {synced ? "Synced" : "Out of sync"} — Last synced: {timestamp}

Design Status: (only display this section if a `design` field exists in the progress file)
  DSL:       {status} — {screenCount} screens — {generatedAt}
  Stitch:    {status} — {screenCount} screens (if screenCount exists) — {generatedAt}
  Prototype: {status} — {path} — Bundle: {bundleStatus: "current" → "up to date", "stale" → "STALE", absent → omit} — {generatedAt}

Stitch status display mapping:
  "completed"   → "completed"
  "stale"       → "STALE (run /planning-plugin:pp-sync-stitch or /planning-plugin:pp-design --stage=stitch)"
  "skipped"     → "skipped"
  "pending"     → omit entire Stitch line
  "in_progress" → "in progress"

Design System: (only display this section if a `designSystem` field exists in the progress file)
  Status: {status} — Domain: {domain} — {generatedAt}

Notion Sync: (only display this section if a `notion` field exists in the progress file)
  {lang_name} ({lang}): {syncStatus_display} — {parentPageUrl} — Last synced: {lastSyncedAt}
  syncStatus display mapping:
    "synced"  → "✓ Synced"
    "syncing" → "⚠ INTERRUPTED"
    "stale"   → "⚠ STALE"

Implementation: (only display this section if an `implementation` field exists in the progress file)
  Status: {status}
  Verification: {pass/fail/—}
  Review: {pass/fail/—}

Open Questions: {count from {feature}-spec.md's Open Questions section}
  1. If there are unresolved issues from the latest review round, list them

If no feature name is provided:

  1. Scan docs/specs/*/ for all feature directories. Skip _shared — it is a pseudo-feature for shared layouts and has no progress file.
  2. Read each progress file
  3. For each spec, determine its target languages from its workingLanguage
  4. Display a summary table with dynamic translation columns based on target languages:
Specifications Overview:
┌──────────────────┬────────────┬───────┬─────────┬─────────┬────────────────────┬───────────┬───────────┐
│ Feature          │ Status     │ Round │ Planner │ Tester  │ Translated         │ Design    │ Notion    │
├──────────────────┼────────────┼───────┼─────────┼─────────┼────────────────────┼───────────┼───────────┤
│ social-login     │ reviewing  │   2   │  7/10   │  6/10   │ ko✓ vi✓            │ —         │ en✓ ko✓   │
│ user-profile     │ finalized  │   3   │  9/10   │  8/10   │ en✓ vi✓            │ ✓ DSL+Pro │ en⚠ ko✓  │
│ notifications    │ drafting   │   0   │   —     │   —     │ ko✗ vi✗            │ —         │ —         │
└──────────────────┴────────────┴───────┴─────────┴─────────┴────────────────────┴───────────┴───────────┘

Notion column uses per-language status symbols:

  • ✓ = synced
  • ⚠ = stale or interrupted (needs re-sync)
  • — = no Notion sync configured
  1. If no specs exist yet, display:

    No specifications found. Run /planning-plugin:pp-spec "feature description" to create one.

04 同仓库更多 Skills

ohmyhotelco
ohmyhotelco/hare-cc-plugins

hp-shared

Shared conventions for every homepage-plugin agent and skill — stack, code conventions, state-file writes, check commands and how to report them. Preloaded into agents through their `skills:` frontmatter; not meant to be invoked by hand.

★ 2
ohmyhotelco
ohmyhotelco/hare-cc-plugins

fe-shared

Shared conventions for every frontend-react-plugin agent and skill — code conventions, state files and locks, accepted deviations, design principles, build working directory, router-mode command matrix, TypeScript check. Preloaded into agents through their `skills:` frontmatter; not meant to be invoked by hand.

前端开发视觉设计
★ 2
ohmyhotelco
ohmyhotelco/hare-cc-plugins

be-spring-shared

Shared conventions for every backend-springboot-plugin agent and skill — tech stack, CQRS architecture, naming, coding standards, TDD, commit and build rules, state files. Preloaded into agents through their `skills:` frontmatter; not meant to be invoked by hand.

后端与接口Skill与智能体开发
★ 2
ohmyhotelco
ohmyhotelco/hare-cc-plugins

pp-translate

Use after directly editing the working language spec to sync changes to other supported languages.

★ 2
ohmyhotelco
ohmyhotelco/hare-cc-plugins

pp-sync-stitch

Use when wireframes were manually edited on the Stitch website and need to be re-fetched to the local project.

Skill与智能体开发
★ 2
ohmyhotelco
ohmyhotelco/hare-cc-plugins

pp-sync-notion

Use when a specification needs to be published or re-synced to Notion after finalization or manual edits.

Skill与智能体开发
★ 2