resumework

Automate a self-looping Cortex development workflow with plan-driven task completion.

3|Updated Jan 12, 2026
One-click install
npx skills add https://github.com/neuro-1977/Cortex --skill resumework
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: resumework
Source: https://github.com/neuro-1977/Cortex/tree/main/.cursor/skills/resumework
Command: npx skills add https://github.com/neuro-1977/Cortex --skill resumework

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a disciplined, self-sustaining workflow to keep Cortex development on track by enforcing a strict, plan-driven loop that restarts after completion steps and prevents feature duplication.

Core Features & Use Cases

  • Autonomous development loop: runs a 10-step process that re-reads the master resume prompt and continues until all tasks are complete.
  • Documentation discipline: requires all documentation to live under data/docs and updates development logs, migration plans, and documentation indices.
  • Governance & consistency: ensures Cortex namespace migration, task tracing, and non-deviation from documented plans.

Quick Start

Activate resumework to start the autonomous Cortex development loop. Then run a full build validation with dotnet build --no-incremental and review the data/docs for tasks.

Frequently Asked Questions about resumework

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

FAQPage Schema
How do I automate an autonomous development loop for long-running feature cycles?

An autonomous development loop runs a 10-step process that re-reads a master resume prompt and continues until all tasks complete, ensuring plan-driven progress without deviating from documented plans.

How do I maintain documentation discipline during namespace migrations and feature development?

Documentation discipline during namespace migrations requires all documentation to live under data/docs, updating development logs, migration plans, and documentation indices throughout the workflow.

What is the best way to prevent feature duplication in Cortex development workflows?

Preventing feature duplication in Cortex development requires a self-sustaining, plan-driven loop that restarts after completion steps and enforces strict task tracing against documented plans.

Can I use an autonomous workflow for consolidating documentation and updating development logs?

Yes, an autonomous self-looping workflow applies to documentation consolidation and migration updates by enforcing a strict loop that updates development logs and documentation indices under data/docs.

How do I validate a build with zero errors during an autonomous Cortex development cycle?

Validating a build with zero errors during a Cortex development cycle requires running a full build validation with dotnet build --no-incremental and reviewing data/docs for pending tasks.

When do I need a self-looping workflow for Cortex namespace migrations?

A self-looping workflow for Cortex namespace migrations is needed for long-running feature cycles requiring task tracing, non-deviation from documented plans, and continuous development log updates.