skills.rest
nishantnaagnihotri
nishantnaagnihotriCOMMUNITY
Explore all skills by this author →
GitHub

slice-traceability-and-issue-ops

Coordinate slice artifacts and issue links with bidirectional traceability.

Updated Jan 30, 2019
Search Tags:#workflow#backlinks#issues#traceability#gate#slices#artifact-management
One-click install
npx skills add https://github.com/nishantnaagnihotri/tark-vitark --skill slice-traceability-and-issue-ops
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: slice-traceability-and-issue-ops
Source: https://github.com/nishantnaagnihotri/tark-vitark/tree/main/.github/skills/slice-traceability-and-issue-ops
Command: npx skills add https://github.com/nishantnaagnihotri/tark-vitark --skill slice-traceability-and-issue-ops

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Slice traceability ensures that gate artifacts and related issues stay synchronized with bidirectional links and consistent metadata, reducing gaps between artifacts and task tracking.

Core Features & Use Cases

  • Enforces creation and linking of slice artifacts under docs/slices/<slice-name>/ with standard file names 01-requirement.md to 06-tasks.md.
  • Maintains bidirectional relationships between the slice tracker issue and all related user-story issues, with backlinks.
  • Validates presence and consistency of required metadata and links before Gate progression.

Quick Start

Run the traceability workflow to verify and synchronize slice artifacts and issue links before Build.

Frequently Asked Questions about slice-traceability-and-issue-ops

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

FAQPage Schema
How do I maintain bidirectional traceability between slice artifacts and issue trackers?▼

Maintain bidirectional slice traceability by coordinating versioned artifacts under docs/slices and linking the slice tracker issue back to all related user-story issues with validated backlinks.

What is the best way to validate required backlinks before closing Gate 4?▼

Validate required backlinks before closing Gate 4 by running a traceability workflow that checks for consistent metadata and synchronized links between slice artifacts and story issues.

How do I enforce standard file naming when creating slice artifacts under docs/slices?▼

Enforce standard slice artifact creation by generating versioned files like 01-requirement.md through 06-tasks.md directly under the docs/slices/<slice-name>/ directory structure.

Does slice traceability require writing 06-tasks.md to synchronize gate artifacts?▼

Yes, writing 06-tasks.md is required to synchronize gate artifacts, as it enforces standard file naming and maintains consistent task tracking metadata before Build progression.

Why does my slice tracker issue lose its links to related user stories?▼

Slice tracker issues lose links when traceability workflows are not applied, failing to validate the required bidirectional backlinks between the tracker and related user-story issues before progression.

Related Skills

Explore More Software Engineering Skills→
buenhydenbuenhyden
1

execution-plan

Convert architecture and design artifacts into structured execution plans.

Community
Intermediate
jeremy-newhousejeremy-newhouse

wa:deploy-review

Enforce deploy readiness gates for dev-to-main promotion with a DEPLOY-REVIEW.md verdict.

Community
Advanced
anhhung04anhhung04
1

github-triage

Automate task creation and status updates from GitHub issues via the API.

Community
Basic
nanorepublicananorepublica
61

Frontend CSS

Enforce frontend CSS coding standards for naming, organization, and responsive design.

Community
Basic