feature

仓库创建 2026年7月6日最近提交 21 天前SkillHot 收录 21 天前
▸ 精选理由

把聊天中决议转换为可审计的文件驱动特性流程

▸ 风险提示

会修改仓库文件,需注意权限与审计

这个 Skill 做什么

管理 /features 下特性全生命周期、状态与审批门禁。

把项目里的功能特性用规范文件管理起来,管整个生命周期、状态流转和审批门槛,方便团队一致执行。用在规划、撰写、审批、跟踪或实现新 feature 的时候,确保谁做了什么、什么通过、什么还卡着都有记录。关键规则是:只有 /features 目录里的文件才算权威来源,聊天里说的临时决定不算数,避免口头或私聊碎片造成脱节。

▸ 展开 SKILL.md 英文原文

Use when planning, specifying, approving, tracking, or implementing new features. Manages the /features lifecycle, state transitions, approval gates, and completion validation.

Skill 开发管理特性规划变更管理审批流程通用
0
Stars
0
Forks
10
仓库内 Skill
+0
7 日增星
安装 / 使用
给你的 Agent 一句话(通用)
帮我安装这个 skill:https://raw.githubusercontent.com/Seismoforg/claude-config/main/skills/feature/SKILL.md
或 curl 直取 SKILL.md
curl -fsSL "https://raw.githubusercontent.com/Seismoforg/claude-config/main/skills/feature/SKILL.md"
SKILL.MD 节选查看完整文件 ↗
# FEATURE SYSTEM

Manages all feature lifecycle ops in `/features`.

Authoritative rule: **only files inside `/features` define feature state.** Chat is never a spec source. A requirement that exists only in chat does not exist until written into a feature file.

# ON ACTIVATION — STATE CHECK FIRST
Before anything else:
0. Bare invocation (no feature named/described) → don't guess. Show current non-terminal features (draft, pending, approved, in-progress, ready-for-done) and ask via AskUserQuestion what to do (include a "Brainstorm a new feature" option → Workflow step 0). Proceed only once a feature/intent is chosen.
1. Identify which feature the request refers to (name or timestamp).
2. Ex
via SKILL·HOT · 数据来自 GitHub 公开信息 · 原文版权归作者所有