원클릭으로 Manus에서 모든 스킬 실행

$pwd:

spec-sync

Name: Spec Sync
Author: lilyLUO233

// Synchronize DEV_SPEC.md and split it into chapter-specific files under specs/ directory. Run sync_spec.py to update, then read SPEC_INDEX.md for navigation. Foundation for all spec-based operations. Use when user says "同步规范", "sync spec", or before any spec-dependent task.

Manus에서 실행

$ git log --oneline --stat

stars:1

forks:0

updated:2026년 2월 5일 08:55

파일 탐색기

3 개 파일

SKILL.md

readonly

name	spec-sync
description	Synchronize DEV_SPEC.md and split it into chapter-specific files under specs/ directory. Run sync_spec.py to update, then read SPEC_INDEX.md for navigation. Foundation for all spec-based operations. Use when user says "同步规范", "sync spec", or before any spec-dependent task.
metadata	{"category":"documentation","triggers":"sync spec, update spec, 同步规范"}
allowed-tools	Bash(python:*) Read

Spec Sync

This skill synchronizes the master specification document (DEV_SPEC.md) and splits it into smaller, chapter-specific files stored in the specs/ directory.

This is a prerequisite for all spec-based operations. Other skills depend on the split spec files to perform their tasks.

How to Use

Used in dev-workflow (Automatic)

When you trigger dev-workflow (e.g., "下一阶段" or "继续开发"), spec-sync runs automatically as Stage 1. No manual action needed.

Manual Sync (Edge Cases Only)

Only manually run if:

You edited DEV_SPEC.md outside of workflow
Spec files are corrupted or missing
Testing a single skill in isolation

# Normal sync
python .github/skills/spec-sync/sync_spec.py

# Force regenerate (even if no changes detected)
python .github/skills/spec-sync/sync_spec.py --force

What the Sync Script Does

The script performs these operations:

Read DEV_SPEC.md from project root
Calculate hash to detect changes
Split the document into chapter files under specs/
Generate SPEC_INDEX.md as the navigation index

After Sync: Navigate with SPEC_INDEX.md

Use SPEC_INDEX.md as your entry point to understand what each spec file contains:

Read: .github/skills/spec-sync/SPEC_INDEX.md

This index file provides:

Summary of each chapter's content
Quick reference to locate the spec you need

Then read the specific spec file you need from specs/ directory:

Read: .github/skills/spec-sync/specs/05-architecture.md

Directory Structure

.github/skills/spec-sync/
├── SKILL.md              ← This file
├── SPEC_INDEX.md         ← Auto-generated index (navigation index)
├── sync_spec.py          ← Sync script
├── .spec_hash            ← Hash file for change detection
└── specs/                ← Split spec files (chapter files)
    ├── 01-overview.md
    ├── 02-features.md
    ├── 03-tech-stack.md
    ├── 04-testing.md
    ├── 05-architecture.md
    ├── 06-schedule.md
    └── 07-future.md

Important Notes

Never edit files in specs/ directly — they are auto-generated
Always edit DEV_SPEC.md and re-run the sync script
Use --force flag to regenerate even if no changes detected:
```
python .github/skills/spec-sync/sync_spec.py --force
```

related-skills.json

같은 저장소

checkpoint.md

from "lilyLUO233/AI_create_code"

Summarize completed work, update progress tracking in DEV_SPEC.md, and prepare for next iteration. Final stage of dev-workflow pipeline. Use when task implementation and testing is completed, or when user says "完成检查点", "checkpoint", "保存进度", "save progress", "任务完成".

2026-02-031

dev-workflow.md

from "lilyLUO233/AI_create_code"

Master orchestrator for development workflow. Use when user says "下一阶段", "继续开发", "next task", "proceed", or asks to continue development. Coordinates spec-sync, progress-tracker, implement, testing-stage, and checkpoint skills in a pipeline to complete one sub-task per iteration.

2026-02-031

implement.md

from "lilyLUO233/AI_create_code"

Implement features following spec-driven workflow. Read specs first, extract design principles, plan file strategy, then write production-ready code with type hints and docstrings. Use when user asks to implement a feature, write code, or build a module. Depends on spec-sync for specification access.

2026-02-031

progress-tracker.md

from "lilyLUO233/AI_create_code"

Identify next development task from project schedule and validate claimed progress against actual codebase state. Serves as GPS for development - tells you where you are and where to go next. Stage 2 of dev-workflow pipeline. Use when user says "检查进度", "status", "下一个任务", "what's next", "定位任务".

2026-02-031

testing-stage.md

from "lilyLUO233/AI_create_code"

Validate implementation through systematic testing after implement stage completes. Determines test type (unit/integration/e2e) based on task nature, runs pytest, and reports results. Stage 4 of dev-workflow pipeline. Use when user says "运行测试", "run tests", "test", or after implementation.

2026-02-031

package.json

"author": "lilyLUO233"

"repository": "lilyLUO233/AI_create_code"

GitHub 저장소 열기 Creator 저장소 보기

$ install --global

$ download --local

Manus에서 실행

$ useful --forSOC

소프트웨어 개발자컴퓨터 및 수학직15-1252L4

name	spec-sync
description	Synchronize DEV_SPEC.md and split it into chapter-specific files under specs/ directory. Run sync_spec.py to update, then read SPEC_INDEX.md for navigation. Foundation for all spec-based operations. Use when user says "同步规范", "sync spec", or before any spec-dependent task.
metadata	{"category":"documentation","triggers":"sync spec, update spec, 同步规范"}
allowed-tools	Bash(python:*) Read

Spec Sync

This skill synchronizes the master specification document (DEV_SPEC.md) and splits it into smaller, chapter-specific files stored in the specs/ directory.

This is a prerequisite for all spec-based operations. Other skills depend on the split spec files to perform their tasks.

How to Use

Used in dev-workflow (Automatic)

When you trigger dev-workflow (e.g., "下一阶段" or "继续开发"), spec-sync runs automatically as Stage 1. No manual action needed.

Manual Sync (Edge Cases Only)

Only manually run if:

You edited DEV_SPEC.md outside of workflow
Spec files are corrupted or missing
Testing a single skill in isolation

# Normal sync
python .github/skills/spec-sync/sync_spec.py

# Force regenerate (even if no changes detected)
python .github/skills/spec-sync/sync_spec.py --force

What the Sync Script Does

The script performs these operations:

Read DEV_SPEC.md from project root
Calculate hash to detect changes
Split the document into chapter files under specs/
Generate SPEC_INDEX.md as the navigation index

After Sync: Navigate with SPEC_INDEX.md

Use SPEC_INDEX.md as your entry point to understand what each spec file contains:

Read: .github/skills/spec-sync/SPEC_INDEX.md

This index file provides:

Summary of each chapter's content
Quick reference to locate the spec you need

Then read the specific spec file you need from specs/ directory:

Read: .github/skills/spec-sync/specs/05-architecture.md

Directory Structure

.github/skills/spec-sync/
├── SKILL.md              ← This file
├── SPEC_INDEX.md         ← Auto-generated index (navigation index)
├── sync_spec.py          ← Sync script
├── .spec_hash            ← Hash file for change detection
└── specs/                ← Split spec files (chapter files)
    ├── 01-overview.md
    ├── 02-features.md
    ├── 03-tech-stack.md
    ├── 04-testing.md
    ├── 05-architecture.md
    ├── 06-schedule.md
    └── 07-future.md

Important Notes

Never edit files in specs/ directly — they are auto-generated
Always edit DEV_SPEC.md and re-run the sync script
Use --force flag to regenerate even if no changes detected:
```
python .github/skills/spec-sync/sync_spec.py --force
```

spec-sync

Spec Sync

How to Use

Used in dev-workflow (Automatic)

Manual Sync (Edge Cases Only)

What the Sync Script Does

After Sync: Navigate with SPEC_INDEX.md

Directory Structure

Important Notes

이 저장소의 다른 Skills

이 저장소의 다른 Skills

Spec Sync

How to Use

Used in dev-workflow (Automatic)

Manual Sync (Edge Cases Only)

What the Sync Script Does

After Sync: Navigate with SPEC_INDEX.md

Directory Structure

Important Notes