skills.rest
Kyonax
KyonaxCOMMUNITY
Explore all skills by this author →
Website𝕏@kyonax_on_techGitHub

reckit-roam-node

Generate and sync org-roam plan nodes with git and GitHub PR state.

Updated May 3, 2024
Search Tags:#git#documentation#github#org-roam#plan management#workflow tracking#requirement validation
One-click install
npx skills add https://github.com/Kyonax/dot-files --skill reckit-roam-node
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reckit-roam-node
Source: https://github.com/Kyonax/dot-files/tree/main/.config/doom-mac/gptel-directives/skills/reckit-roam-node
Command: npx skills add https://github.com/Kyonax/dot-files --skill reckit-roam-node

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually tracking software project plans, decisions, and progress across org-roam, git, and GitHub PRs leads to out-of-sync records, missed workflow state updates, and inconsistent documentation. This Skill automates the creation and maintenance of structured org-roam plan nodes for the Reckit project, eliminating manual sync work and ensuring documentation always matches actual development state.

Core Features & Use Cases

  • Structured Plan Node Generation: Creates three consistent org-roam node templates for Standard Feature plans, Bug fix plans, and Release plans, with standardized metadata, requirement tracking, decision logging, and phased task lists.
  • Automated Index Dashboard Sync: Maintains a two-layer Reckit index (BACKLOG source of truth + PLAN BOARD workflow view) that automatically derives plan progress lanes from live git branch and GitHub PR state, tracking plans through IN PLANNING, IN DEVELOPMENT, IN REVIEW, IN TEST, and ALL RELEASED stages.
  • Validation and Traceability: Validates implemented code against plan requirements, captures post-implementation findings, and cross-references decisions with the project's canonical session file for full auditability.
  • Use Case: A developer working on a new OBS HUD web source feature can use this Skill to draft a plan node during a planning conversation, automatically track its progress via the index dashboard as commits and PRs are created, and validate that the final implementation matches the original requirements before merge.

Quick Start

Use the reckit-roam-node skill to create a new feature plan node for the context-screen web source, then sync the Reckit index dashboard to reflect its current development lane.

Frequently Asked Questions about reckit-roam-node

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

FAQPage Schema
How do I sync org-roam plan nodes with git branch and GitHub PR state?▼

You can sync org-roam plan nodes with git branch and GitHub PR state by automating generation and maintenance of structured plan nodes. This ensures a two-layer index dashboard automatically derives plan progress lanes directly from live repository states.

What is the best way to track software project plans across org-roam and GitHub?▼

The best way to track software project plans across org-roam and GitHub is using an automated two-layer index. It maintains a BACKLOG source of truth and a PLAN BOARD workflow view, tracking plans through IN PLANNING to ALL RELEASED stages based on live repository state.

How do I create structured org-roam nodes for feature, bug fix, and release plans?▼

You create structured org-roam nodes for feature, bug fix, and release plans by using standardized templates that enforce consistent plan metadata, requirement validation, decision logging, and phased task lists for full traceability.

Can I validate implemented code against original plan requirements in org-roam?▼

Yes, you can validate implemented code against plan requirements in org-roam. The process validates implemented code, captures post-implementation findings, and cross-references decisions with the project's canonical session file for full auditability.

Does this org-roam workflow tracking require manual updates when PRs are created?▼

No, this org-roam workflow tracking does not require manual updates when PRs are created. It eliminates manual sync work by automatically tracking plan progress via the index dashboard as commits and PRs are created.

Why do my org-roam software development records get out of sync with GitHub?▼

Org-roam software development records get out of sync with GitHub due to manually tracking plans and decisions across separate systems, which leads to missed workflow state updates. Automating node generation and dashboard syncing resolves this by enforcing consistent metadata.

Related Skills

Explore More Software Engineering Skills→
majorgreysmajorgreys
35

Org-roam Note Management

Automates org-roam note creation, search, linking, tagging, and diagnostics via emacsclient.

Community
Advanced
EduardoJVNEduardoJVN

sdd-verify

Validate code implementations against project specifications and design documents.

Community
Advanced
KyonaxKyonax

mr-roam-node

Translates JIRA tickets into standardized org-roam nodes with GIVEN/WHEN/THEN acceptance criteria.

Community
Advanced
addisonbeckaddisonbeck

create_memory

Create org-roam memory nodes with validated metadata and UUIDs.

Community
Intermediate