continue-implementation

Name: continue-implementation
Availability: InStock
Author: LibPDF

Locate and load a spec from .agents/plans/ to continue implementation until tests pass.

1.8k|62|Updated Jan 11, 2026

Search Tags:#automation #git #architecture #spec #tests #continue-implementation

Ready to run

npx skills add https://github.com/LibPDF-js/core --skill continue-implementation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: continue-implementation
Source: https://github.com/LibPDF-js/core/tree/main/.opencode/skills/continue-implementation
Command: npx skills add https://github.com/LibPDF-js/core --skill continue-implementation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you resume work on a formal specification from a prior session, ensuring continuity and reducing setup time when picking up stalled tasks.

Core Features & Use Cases

Autonomous spec continuation: Identify the target spec, load it, and resume implementation without manual prompting.
Architecture-guided execution: Follow the project's layered guidance (ARCHITECTURE.md) and coding standards (CODE_STYLE.md) while progressing.
Progress planning and tracking: Assess current state, plan remaining work with TodoWrite, and drive tests until completion.

Quick Start

Use this Skill to locate the relevant spec under .agents/plans/, load it, and continue implementing until tests pass.

Frequently Asked Questions about continue-implementation

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

FAQPage Schema

How do I resume implementing a spec from a previous session?▼

Resuming spec implementation from a previous session involves locating the target spec file in .agents/plans/ and continuing work with minimal prompts. It assesses the current state via git and tests before planning remaining tasks.

How does autonomous spec continuation work with existing architecture guidelines?▼

Autonomous spec continuation works with existing architecture guidelines by ensuring adherence to ARCHITECTURE.md and CODE_STYLE.md while progressing. It follows the project's layered guidance to maintain standards during task resumption.

Do I need git and tests to assess the current state before resuming a stalled task?▼

Yes, you need git and tests to assess the current state before resuming a stalled task. The process evaluates the repository status via git and runs tests to determine what implementation work remains before planning with TodoWrite.

What's the best way to plan remaining work when picking up stalled project maintenance tasks?▼

The best way to plan remaining work when picking up stalled project maintenance tasks is using TodoWrite after assessing the current state via git and tests. It drives implementation forward until all tests pass.

Can I finalize a specification without manual prompting across the repository?▼

Yes, you can finalize a specification without manual prompting across the repository. It applies to project maintenance tasks by autonomously identifying the target spec, loading it, and continuing implementation until completion.