implement

Execute the ARCH to LIB governance workflow from Jira keys or JSON context files.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/ResearchMonkey/Foundation_template --skill implement-researchmonkey
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/ResearchMonkey/Foundation_template/tree/main/.claude/skills/implement
Command: npx skills add https://github.com/ResearchMonkey/Foundation_template --skill implement-researchmonkey

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Unified governance workflow for AI-driven software projects, coordinating the full board lifecycle (ARCH → SEC → QA → OPS → LIB) from simple inputs like Jira keys, URLs, or JSON context files.

Core Features & Use Cases

  • End-to-end governance sequence: Orchestrates ARCH → SEC → QA → OPS → LIB across issues and decisions.
  • Flexible inputs: Accepts Jira keys, URLs, or JSON context files to start workflows.
  • Interactive and CI parity: Works identically in interactive sessions and CI environments.
  • Cross-tool compatibility: Tool-agnostic design across Claude Code, Cursor, and Grok.

Quick Start

Provide a Jira key or URL to begin the board workflow, or supply a JSON context file to initialize the process.

Frequently Asked Questions about implement

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

FAQPage Schema
How do I automate Jira board governance workflows across CI environments?

Automate Jira board governance by accepting a Jira key or URL to drive the full ARCH, SEC, QA, OPS, and LIB sequence, executing identically in interactive sessions and CI environments with deterministic state transitions.

Can I use a JSON context file to initialize an end-to-end software governance workflow?

Initialize the governance workflow by supplying a JSON context file to trigger the ARCH, SEC, QA, OPS, and LIB lifecycle orchestration, ensuring consistent tool-agnostic execution across Claude Code, Cursor, and Grok.

Does this governance workflow tool support cross-compatibility with Cursor and Grok?

The governance workflow supports cross-tool compatibility across Claude Code, Cursor, and Grok, maintaining tool-agnostic execution and strict input validation to guard against invalid inputs and partial runs.

What is the best way to orchestrate board work across multiple AI coding tools?

Orchestrate board work by feeding a Jira key into the unified workflow, which coordinates the full board lifecycle across AI tools while enforcing strict input validation and robust error handling for partial runs.

How do I prevent partial runs and invalid inputs in automated CI governance sequences?

Prevent partial runs and invalid inputs through strict input validation and robust error handling built into the governance workflow, ensuring deterministic state transitions across both interactive and CI environments.

When do I need an end-to-end governance sequence for AI-driven software projects?

An end-to-end governance sequence is needed when coordinating the full board lifecycle from ARCH to LIB across AI-driven projects, requiring deterministic state transitions and tool-agnostic execution across various environments.