Translate NONoise sprint manifest macro tasks into external issue tracker work items.
npx skills add https://github.com/russosalv/NONoise --skill spec-to-workitem
Please help me install this Agent Skill. Skill: spec-to-workitem Source: https://github.com/russosalv/NONoise/tree/main/packages/skills/spec-to-workitem Command: npx skills add https://github.com/russosalv/NONoise --skill spec-to-workitem
Translates macro functional tasks from a NONoise sprint manifest into external issue tracker work items so teams can reliably populate backlogs without manual copy-paste, duplicate issues, or credential leakage. It enforces idempotency, previews changes in dry-run mode, and centralizes tracker-specific logic in pluggable adapters so the source-of-truth is never mutated inadvertently.
Run the spec-to-workitem skill to dry-run export Sprint 5 to GitHub issues.
High-intent search queries and answers about installing and using this skill.
You can export sprint tasks to issue trackers by running a dry-run preview first, then applying adapter-driven creation with idempotent external_id matching and two-pass dependency linking to populate backlogs safely.
Yes, you can preview backlog items before creating work items in Azure DevOps by using dry-run mode, which classifies tasks as NEW, EXISTS, or AMBIGUOUS and reports changes without mutating the source-of-truth or pushing to the tracker.
Idempotent work item creation prevents duplicate issues in Linear or Jira by searching for existing items by task ID via adapter contracts, classifying matches, and asking before updating, ensuring repeated exports do not create redundant tracker entries.
Yes, you need environment variables to authenticate with GitHub Issues and Azure DevOps adapters, as the export process applies adapter-based authentication through environment variables and stops execution immediately upon detecting authentication failures.
When transient errors occur during sprint manifest export to issue trackers, the process retries with backoff and reports per-item failures without aborting the entire run, allowing successful items to complete while isolating individual errors.
Task dependencies and metadata are mapped during export using a two-pass creation process that resolves dependency links first, then maps effort, components, confidence labels, and sprint or milestone fields according to each tracker's specific adapter contract.
arozumenkoCreate, query, update, and close issues across GitHub, GitLab, Jira, Azure DevOps, and Linear.
ViktorBarzinDiagnose Kubernetes NFS mount failures causing ContainerCreating pod states.
danielbushManage work items, tickets, and session histories in a work/ directory.
joestumpCoordinate parallel tracker issue implementation via deterministic git worktrees and automated PRs.
