skills.rest
AndreJorgeLopes
AndreJorgeLopesCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

writing-plans

Extend writing-plans to hand off plan state to the lock-tests phase.

1|Updated Mar 3, 2026
Search Tags:#planning#writing#Claude Code#workflows#ticket tracking#session orchestration#phase handoff
One-click install
npx skills add https://github.com/AndreJorgeLopes/devflow --skill writing-plans-andrejorgelopes
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/AndreJorgeLopes/devflow/tree/main/skills/writing-plans
Command: npx skills add https://github.com/AndreJorgeLopes/devflow --skill writing-plans-andrejorgelopes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing plans often end without a reliable handoff to the next implementation or testing phase, causing wasted momentum and inconsistent state between sessions.

Core Features & Use Cases

  • Extends superpowers:writing-plans with devflow’s phase-handoff at completion, keeping the workflow consistent.
  • Creates a plan checkpoint by detecting the ticket ID from the current branch and marking a chapter so the phase is visible in Claude Code/desktop flows.
  • Initiates a fresh next-session phase by invoking devflow:phase-handoff with the plan phase and the next phase set to lock-tests, ensuring the lock phase starts in the spawned session.

Quick Start

Ask your AI agent to run the writing-plans skill on your feature branch so it saves the plan and hands off to lock-tests.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I transition a writing plan into the next development phase in Claude Code?▼

To transition a writing plan into the next development phase in Claude Code, the skill detects the ticket ID from your feature branch and invokes devflow:phase-handoff to freeze the plan state and spawn the lock-tests phase.

What is phase handoff in ticket-based implementation planning?▼

Phase handoff in ticket-based implementation planning is the process of freezing the completed writing plan state and spawning a fresh session for the lock-tests phase, ensuring consistent workflow momentum without losing context.

How do I automate session orchestration for lock-tests after writing plans?▼

You automate session orchestration for lock-tests by running the writing-plans skill on your feature branch, which writes the frozen plan state and spawns the next lock-tests phase without auto-invoking it.

Does the writing-plans workflow require a specific branch naming convention?▼

Yes, the writing-plans workflow requires branch ticket detection, meaning your current Git branch name must contain a ticket ID so the skill can identify the target work and create a plan checkpoint.

Why does my writing plan lose momentum between development sessions?▼

Writing plans lose momentum between development sessions due to inconsistent state handoff, which this skill solves by extending superpowers:writing-plans with a devflow:phase-handoff invocation that reliably freezes state and spawns the next phase.

Related Skills

Explore More Software Engineering Skills→
kristofferrembackkristofferremback
2

commit

Create conventional git commit messages from staged changes with Linear ticket IDs.

Community
Basic
SamyakJhaveriSamyakJhaveri

plan-review-invoke

Invoke the canonical plan-reviewer prompt on a selected plan in Claude Code sessions.

Community
Intermediate
huydepzai121huydepzai121
3

template-skill

Fill placeholders in templates with supplied data to generate documents.

Community
Basic
Taek-DTaek-D

harness-progress

Track session progress and state using JSON logs and Git commits.

Community
Advanced