feature-readiness
Use when deciding whether a planned feature can move into implementation, including blocker analysis and artifact decisions.
- License 许可
- MIT
- 最近更新
- 2026-07-21
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- feature-readiness
- description
- Use when deciding whether a planned feature can move into implementation, including blocker analysis and artifact decisions.
03 SKILL.md 正文
Feature Readiness
Use this skill before implementing formal T1/T2 features or when the user asks whether a feature is ready.
Scope
- Validate problem, goal, non-goals, and user-facing behavior
- Check scope boundaries and acceptance criteria
- Identify legal, AI, runbook, release, analytics, and data side effects
- Decide whether readiness blocks implementation
- Produce an implementation handoff
Default workflow
- Read
AGENTS.md,agent-execution-contract.md, and the feature owner doc. - Confirm risk tier and task class.
- Review acceptance criteria for testability.
- Check side-effect triggers.
- Decide
Ready for IN_PROGRESS,Blocked, orNeeds planning. - Record the verdict in the feature owner doc.
Output format
Report:
- readiness verdict
- blockers
- required artifacts
- implementation handoff
- verification path
04 同仓库更多 Skills
implementation-surface
Use when implementing or reviewing project-specific application code after feature lifecycle handoff.
governance-kit-operator
Use when installing, refreshing, or operating Agentic Doc Governance Kit in a target repo, including init dry-runs, generated governance files, feature lifecycle CLI usage, checks, and final user reports. Use this whenever the user asks an AI agent to set up this kit, apply it to another project, initialize governance docs, create governed feature work, or explain the operational workflow.
feature-lifecycle
Use when adding, planning, updating, verifying, closing out, archiving, or relocating a project feature under the repo's documentation governance model.
feature-lifecycle
Example lifecycle skill.
governance-kit-target-smoke
Use when validating that Agentic Doc Governance Kit initializes correctly into a target repository, including init dry-runs, generated file presence, installed skills, docs checks, skills checks, and optional feature lifecycle CLI smoke tests. Use this whenever the user asks to test install output, verify init behavior, or confirm generated templates work in a target repo.
governance-kit-skill-authoring
Use when creating, renaming, reviewing, or updating repo-local skills for Agentic Doc Governance Kit, including skill frontmatter, required sections, registry updates, generated footprint entries, README project shape, changelog notes, and skills integrity checks. Use this whenever the user asks to turn a workflow into a skill or add a skill to this kit.