rulebook-task-archive

Archive a completed Rulebook task to the archive directory with date prefix. Use after a task is fully implemented and validated.

11 stars

Best use case

rulebook-task-archive is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Archive a completed Rulebook task to the archive directory with date prefix. Use after a task is fully implemented and validated.

Teams using rulebook-task-archive should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/rulebook-task-archive/SKILL.md --create-dirs "https://raw.githubusercontent.com/hivellm/rulebook/main/skills/rulebook-task-archive/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/rulebook-task-archive/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How rulebook-task-archive Compares

Feature / Agentrulebook-task-archiveStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Archive a completed Rulebook task to the archive directory with date prefix. Use after a task is fully implemented and validated.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# rulebook_task_archive

Archive a completed Rulebook task.

## Input Schema

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `taskId` | string | Yes | Task ID to archive |
| `skipValidation` | boolean | No | Skip validation before archiving (default: false) |

## Usage

```typescript
// Archive with validation (recommended)
await mcp.rulebook_task_archive({ taskId: "add-auth-system" });

// Archive without validation
await mcp.rulebook_task_archive({ taskId: "add-auth-system", skipValidation: true });
```

## Response

```json
{
  "success": true,
  "taskId": "add-auth-system",
  "message": "Task add-auth-system archived successfully"
}
```

## Archive Location

Tasks are moved to: `rulebook/tasks/archive/YYYY-MM-DD-<task-id>/`

## When to Use

- After task implementation is complete
- After all tests pass and task is validated
- To clean up the active tasks list

Related Skills

rulebook-typescript

11
from hivellm/rulebook

TypeScript development with strict mode, Vitest testing, ESLint linting, and CI/CD best practices. Use when working on TypeScript projects, writing tests, configuring linting, or setting up build pipelines.

rulebook-task-validate

11
from hivellm/rulebook

Validate a Rulebook task format and structure against OpenSpec requirements. Use before archiving or to verify task quality.

rulebook-task-update

11
from hivellm/rulebook

Update a Rulebook task status. Use to mark tasks as in-progress, completed, or blocked.

rulebook-task-show

11
from hivellm/rulebook

Show complete details of a Rulebook task including proposal, checklist, design, and specs. Use to understand task requirements before implementation.

rulebook-task-management

11
from hivellm/rulebook

Spec-driven task management for features and breaking changes using OpenSpec format. Use when creating new features, planning breaking changes, organizing development work, or managing project tasks with proposals and specifications.

rulebook-task-list

11
from hivellm/rulebook

List all Rulebook tasks with optional status filtering and archive inclusion. Use to check project tasks, progress, or find tasks by status.

rulebook-task-delete

11
from hivellm/rulebook

Permanently delete a Rulebook task. Cannot be undone. Prefer archiving completed tasks instead.

rulebook-task-create

11
from hivellm/rulebook

Create a new Rulebook task with standardized directory structure. Use when starting a new feature, breaking change, or architectural work that needs spec-driven planning.

rulebook-skill-validate

11
from hivellm/rulebook

Validate the current skills configuration for conflicts, missing dependencies, and errors. Use to ensure skills are properly configured.

rulebook-skill-show

11
from hivellm/rulebook

Show detailed information about a specific skill including metadata, content preview, and enabled status. Use to inspect a skill before enabling it.

rulebook-skill-search

11
from hivellm/rulebook

Search for skills by name, description, or tags. Use to find skills matching specific requirements or technologies.

rulebook-skill-list

11
from hivellm/rulebook

List all available Rulebook skills, optionally filtered by category or enabled status. Use to discover what skills are available for the project.