mission-skip

Skip pending mission features and update associated assertions to 'skipped'.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/originlabs-app/claude-codex-missions --skill mission-skip
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mission-skip
Source: https://github.com/originlabs-app/claude-codex-missions/tree/main/claude/.claude/skills/mission-skip
Command: npx skills add https://github.com/originlabs-app/claude-codex-missions --skill mission-skip

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill allows users to bypass specific pending features within an active mission, preventing them from blocking mission completion and marking them as intentionally skipped.

Core Features & Use Cases

  • Feature Skipping: Mark individual features as 'skipped' with an optional reason.
  • Assertion Management: Automatically marks all assertions related to a skipped feature as 'skipped' as well.
  • State Update: Updates mission state files (features.json, validation-state.json, state.json, progress_log.jsonl) to reflect the skipped status.
  • Use Case: If a feature in a software development mission becomes irrelevant or blocked by external factors, this Skill can be used to remove it from the current iteration without halting progress on other features.

Quick Start

Use the mission-skip skill to skip feature with ID 'feat-123' and provide the reason 'external dependency not met'.

Frequently Asked Questions about mission-skip

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

FAQPage Schema
How do I skip a pending feature in an active mission without blocking progress?

Skipping a pending feature updates its status to skipped along with an optional reason. This action modifies mission state files including features.json, validation-state.json, state.json, and progress_log.jsonl to reflect the deferred status.

What happens to assertions when a feature is skipped in project management workflows?

When a feature is skipped, all associated assertions are automatically marked as skipped as well. This ensures validation-state.json remains consistent without requiring manual updates to individual feature checks.

When should I defer or remove features from active consideration in iterative development?

You should defer features when they become irrelevant or blocked by external factors in a software development mission. This removes them from the current iteration without halting progress on other active features.

Can I provide a specific reason when marking a mission feature as skipped?

Yes, you can provide an optional reason when skipping a pending feature. For example, you can skip a feature with a specific ID and specify the reason as an unmet external dependency.

Does skipping a feature affect the overall mission state counts and progress logs?

Yes, skipping a pending feature updates state.json to adjust overall state counts and appends an entry to progress_log.jsonl. This maintains an accurate record of mission progress and current feature statuses.

What's the best way to manage mission state files when deferring software development features?

The best way is to use a dedicated workflow tool that automatically manages mission state files like features.json, validation-state.json, state.json, and progress_log.jsonl in a single operation when deferring features.