skills.rest
aditrioka
aditriokaCOMMUNITY
Explore all skills by this author →
GitHub

next-change

Identify and claim the next OpenSpec change for the nearyou-id project.

Updated Apr 22, 2026
Search Tags:#project management#change management#openspec#proposal management#nearyou-id
One-click install
npx skills add https://github.com/aditrioka/nearyou-id --skill next-change
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: next-change
Source: https://github.com/aditrioka/nearyou-id/tree/main/.claude/skills/next-change
Command: npx skills add https://github.com/aditrioka/nearyou-id --skill next-change

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires OpenSpec, git, GitHub, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill assists in identifying and managing the next OpenSpec change for the nearyou-id project, including claiming and proposing changes.

Core Features & Use Cases

  • Change Identification: Automatically surveys in-flight PRs and branches to identify the next change.
  • Claim Management: Immediately claim a change by creating a draft PR, preventing concurrent selections.
  • Proposal Scaffold: Scaffold an OpenSpec proposal onto the claimed branch.
  • Review Coordination: Facilitate review by sub-agents during the proposal phase.
  • Handoff to Implementation: Transition the change to implementation phase after review.

Quick Start

Run the 'next-change' skill to suggest the next change for the nearyou-id project.

Frequently Asked Questions about next-change

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I identify and claim the next OpenSpec change for my project?▼

To identify the next OpenSpec change, this skill surveys in-flight PRs and branches. It immediately claims the change by creating a draft PR, preventing concurrent selections and managing session coordination.

How does proposal management work with OpenSpec and git branches?▼

OpenSpec proposal management scaffolds a proposal directly onto a claimed git branch. It coordinates drafting, facilitates sub-agent review, and transitions the change to implementation handoff after proposal approval.

Do I need GitHub and OpenSpec to track project proposals automatically?▼

Yes, OpenSpec and GitHub are required dependencies for tracking project proposals. The skill uses git branches and draft PRs to manage change reservation and coordinate session concurrency.

What is the best way to prevent concurrent OpenSpec change selections in a repository?▼

The best way to prevent concurrent OpenSpec selections is claim management via draft PRs. This skill creates a draft PR to immediately reserve a change, ensuring no other sessions can select or propose the same modification.

How do I coordinate proposal review and handoff to implementation using OpenSpec?▼

To coordinate proposal review, this skill facilitates sub-agent reviews during the proposal phase on the claimed branch. After review, it automatically transitions the OpenSpec change to the implementation phase.

Why does next-change require OpenSpec and git for change management?▼

Next-change requires OpenSpec and git because change management depends on branch structures and PR workflows. These tools provide the necessary infrastructure to reserve changes, scaffold proposals, and track implementation handoff.

Related Skills

Explore More Product & Management Skills→
MakisuoMakisuo
1.6k

clickhousectl-local-dev

Install and configure a local ClickHouse environment with clickhousectl.

Community
Intermediate
jankneumannjankneumann

linear-cleanup-feature

Merge approved OpenSpec feature pull requests and archive proposals.

Community
Advanced
BEIRUXBEIRUX

doc-coauthoring

Guide collaborative drafting of technical specs, proposals, and decision records.

Official
Intermediate
guhans6guhans6

triage

Automate issue classification and state transitions in project trackers.

Community
Intermediate