skills.rest
danielbaustin
danielbaustinCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

stp-editor

Normalize and tighten STP task cards while preserving issue intent and lifecycle boundaries.

4|1|Updated Feb 3, 2026
Search Tags:#validation#normalization#editor#lifecycle#prompt-template#stp#task-card
One-click install
npx skills add https://github.com/danielbaustin/agent-design-language --skill stp-editor
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: stp-editor
Source: https://github.com/danielbaustin/agent-design-language/tree/main/adl/tools/skills/stp-editor
Command: npx skills add https://github.com/danielbaustin/agent-design-language --skill stp-editor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps teams tighten and normalize STP task cards without altering the underlying issue intent or lifecycle boundaries.

Core Features & Use Cases

  • Normalize STP structure and field shape
  • Tighten goal, required outcome, acceptance criteria, and scope
  • Remove placeholders and mismatched wording to preserve intent and lifecycle boundaries
  • Stop before branch/worktree actions, implementation, or output-card authoring

Quick Start

Read the STP, preserve scope and milestone context, and emit a structured edit result.

Frequently Asked Questions about stp-editor

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

FAQPage Schema
How do I normalize task card structure without changing the original issue intent?▼

Normalize task cards by applying a bounded, template-safe editing approach that tightens goals, acceptance criteria, and scope while strictly preserving the original issue intent and lifecycle boundaries.

What is the best way to tighten acceptance criteria and scope in a prompt-template task card?▼

Tightening acceptance criteria in a prompt-template task card involves removing placeholders and mismatched wording, clarifying required outcomes, and stopping before any branch, worktree, or implementation actions are taken.

Can I use structured editing to remove placeholders from STP documents without triggering implementation?▼

Yes, you can use structured editing to remove placeholders from STP documents. The process validates constraints and explicitly stops before executing branch, worktree, implementation, or output-card authoring actions.

Does STP document normalization support validation of field shape and milestone context?▼

STP document normalization supports validation of field shape and milestone context. It reads the STP, preserves scope, validates constraints, and outputs a concise edited STP at the specified target location.

What are the limitations of bounded editing for task cards?▼

The limitation of bounded editing for task cards is that it stops before branch or worktree actions, implementation, or output-card authoring, ensuring the tool only normalizes structure and wording without writing code.

Related Skills

Explore More Software Engineering Skills→
rhuangabrielsantosrhuangabrielsantos

cy-execute-task

Execute PRD tasks end-to-end from specification to tracking updates.

Community
Advanced
dmedina-devdmedina-dev
1

executing-plans

Execute written implementation plans with stepwise verification in isolated git worktrees.

Community
Intermediate
amo-tech-aiamo-tech-ai

dev-checker

Automate pre-commit checks for TypeScript builds, linting, and repository hygiene.

Community
Intermediate
pchemguypchemguy

spreadsheet

Automate spreadsheet creation, editing, and analysis with openpyxl and pandas.

Community
Intermediate