work-jiang-feature-checklist

Organize Jiang feature implementation workflows with structured scope, verification, and commit checklists.

Updated Feb 8, 2026
One-click install
npx skills add https://github.com/rbtkhn/grace-mar --skill work-jiang-feature-checklist
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: work-jiang-feature-checklist
Source: https://github.com/rbtkhn/grace-mar/tree/main/.cursor/skills/work-jiang-feature-checklist
Command: npx skills add https://github.com/rbtkhn/grace-mar --skill work-jiang-feature-checklist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents multi-step Jiang implementation work from becoming difficult to review by providing a structured checklist for scope control, verification, and commit hygiene.

Core Features & Use Cases

  • Implementation Planning Guardrails: Guides branch hygiene, lane selection, scope boundaries, and plan alignment before starting complex Jiang work.
  • Verification Workflow Support: Defines canonical validation sequences for metadata, scripts, CI changes, and research pipeline updates.
  • Handoff and Review Discipline: Helps operators preserve context through checkpoints, clean diffs, and explicit post-implementation summaries.

Quick Start

Use the work-jiang feature checklist skill to prepare a reviewable implementation plan for a Jiang lane change.

Frequently Asked Questions about work-jiang-feature-checklist

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

FAQPage Schema
How do I keep multi-file feature changes reviewable across a git workflow?

Maintain reviewable multi-file feature changes by applying a structured checklist for scope control, canonical validation sequences, and commit discipline. This approach prevents complex implementation threads from generating unreviewable diffs.

What is the best way to organize branch hygiene and scope boundaries for repository updates?

Organize branch hygiene and scope boundaries for repository updates by defining implementation planning guardrails that guide lane selection and plan alignment. This ensures structured operator coordination across multi-file threads before validation begins.

How do I structure validation workflows for CI extensions and script changes?

Structure validation workflows for CI extensions and script changes by following canonical validation sequences specific to your repository. This ensures metadata, scripts, and research pipeline updates adhere to gated workflow boundaries before commit.

Can I use a checklist workflow for coordinating multi-file implementation threads across operators?

Yes, a checklist workflow supports multi-file implementation threads requiring structured operator coordination. It enforces implementation planning guardrails and preserves context through checkpoints and explicit post-implementation summaries.

When do I need a structured commit discipline process for research pipeline updates?

You need a structured commit discipline process for research pipeline updates when changes involve multiple files, CI extensions, or scripts. Applying scope boundaries and gated workflow boundaries keeps the implementation thread aligned and reviewable.