jinn-archive

Close Linear projects and surface follow-up issues before archiving.

1|Updated Sep 2, 2019
One-click install
npx skills add https://github.com/hackefeller/hominem --skill jinn-archive
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jinn-archive
Source: https://github.com/hackefeller/hominem/tree/main/.claude/skills/jinn-archive
Command: npx skills add https://github.com/hackefeller/hominem --skill jinn-archive

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Close Linear projects, issues, and follow-up work by cleaning up completed work and surfacing necessary follow-ups before archiving.

Core Features & Use Cases

  • Verify Linear MCP is available and list affected issues to determine what remains open
  • Mark the parent Linear project as Done after all sub-issues are completed or properly deferred
  • Post a completion summary detailing what was delivered, what was deferred, and lessons learned for future work
  • Surface and link follow-up work (new or continued issues) to ensure nothing is lost when archiving
  • Enforce guardrails: use Linear MCP tooling, surface incomplete items, and require a named home for deferred work
  • Provide a clean handoff for project archival and reporting

Quick Start

Run the jinn-archive workflow on a completed Linear project to close it and surface follow-up issues.

Frequently Asked Questions about jinn-archive

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

FAQPage Schema
How do I close a Linear project and archive completed work?

Closing a Linear project requires verifying all sub-issues are completed or deferred, marking the parent project as Done, posting a completion summary, and surfacing follow-up tasks before archiving to ensure a clean handoff.

How do I surface follow-up tasks before archiving a Linear project?

Surfacing follow-up tasks involves identifying incomplete issues within the Linear project and linking them to new or continued issues, ensuring deferred work has a named home so nothing is lost during project archival.

What is the best way to handle deferred issues when finalizing Linear milestones?

Handling deferred issues requires enforcing guardrails that mandate a named home for deferred work, ensuring you resolve or defer issues and link them to follow-up tasks before marking the Linear milestone as Done.

Do I need a Linear MCP server to automate project cleanup and completion summaries?

Yes, automating Linear project cleanup requires a configured Linear MCP server. The workflow uses this tooling to list affected issues, enforce guardrails, and post completion summaries detailing what was delivered and deferred.

What should be included in a Linear project completion summary?

A Linear project completion summary should detail what was delivered, what was deferred, and lessons learned for future work, providing clean handoff reporting for project archival and surfacing linked follow-up work.

Why does my Linear project archival fail if issues remain open?

Linear project archival fails when issues remain open because the workflow enforces guardrails to surface incomplete items, requiring you to complete or properly defer all sub-issues to a named home before marking the parent project as Done.