continue-building

Resumes interrupted development tasks by reading scratchpad plans and git history.

2|Updated Feb 15, 2026
One-click install
npx skills add https://github.com/SkinnnyJay/simpill-utils --skill continue-building-skinnnyjay
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: continue-building
Source: https://github.com/SkinnnyJay/simpill-utils/tree/main/.claude/skills/continue-building
Command: npx skills add https://github.com/SkinnnyJay/simpill-utils --skill continue-building-skinnnyjay

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When development work spans multiple sessions, context is lost and it is hard to remember where you left off. This Skill restores task context automatically so work can resume without manual reconstruction of prior state. ## Core Features & Use Cases - Context Recovery: Reads scratchpad/plan.md and active scratchpad files, plus recent git status and commit history, to reconstruct the current task state. - Task Prioritization: Identifies the highest-priority incomplete checklist item and continues implementation from the last checkpoint. - Quality Gates: Enforces typecheck, lint, test, and build verification before marking any task complete. - Use Case: You return to a TypeScript project after a break. The Skill reads your plan file, finds the next unchecked task, implements it with strict typing and Zod validation, runs all quality gates, and updates the scratchpad with progress. ## Quick Start Resume work on my project by reading the scratchpad plan and picking up the next incomplete task.

Frequently Asked Questions about continue-building

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

FAQPage Schema
How do I resume work on a project after a break?▼

Resume work by reading the scratchpad plan files to recover task context, then checking git status and recent commits to see the latest changes. The Skill identifies the highest-priority incomplete checklist item and continues implementation from the last checkpoint.

How to track development tasks across multiple coding sessions?▼

Track tasks as markdown checklist items in a scratchpad plan file, marking completed items with [X] after each session. Combined with git history, this provides enough context to resume work without losing progress between sessions.

What quality checks run before marking a task done?▼

Four quality gates must pass: npm run typecheck with zero errors, npm run lint with zero errors, npm test with all tests passing, and npm run build compiling cleanly. A task is only marked complete after all gates succeed.

When does the Skill stop and ask for guidance?▼

It stops when encountering unresolvable type errors, failing tests, or build errors, when architectural decisions need user input, or when requirements are missing or scope is unclear. It does not guess on ambiguous decisions.

Does this work with projects that have no scratchpad files?▼

The workflow depends on scratchpad plan files for task context, so a project without them loses the primary recovery mechanism. Git status and recent commit history still provide partial context, but task prioritization requires the checklist.