Skip to content
cccskills
FreePublished on GitHub

charted-scaffold

Writes work-in-progress code and tests based on design doc

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md2.3 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Context

  • designDocPath: $ARGUMENTS[0]
  • prNumber: $ARGUMENTS[1]

Task

Based on the following design doc ${designDocPath}, write WIP code for implementation described in the design doc.

  • Focus only on the PR #${prNumber} if provided.
  • If you add a new class, function, or method, make it throw a "🚧 work in progress" error and add the "@deprecated 🚧 work in progress" tag to its jsdoc.
  • If you add a new component, add the "@deprecated 🚧 work in progress" tag to its jsdoc but do not implement the template or methods.
  • DO NOT ADD ANY NEW BEHAVIOR.
    • As an example, do not add child components in a component.
  • DO NOT CHANGE ANY EXISTING BEHAVIOR:
    • If you change a function or a method signature in a retro-compatible way, do not throw a "🚧 work in progress" error.
    • If the function or method receives a new optional parameter, make it throw a "🚧 work in progress" error if the parameter is set.
    • Even if the goal of the PR is to change the behavior of an existing function or method, do not throw a "🚧 work in progress" error. KEEP THE EXISTING BEHAVIOR.
  • For WIP tests, put the test's steps from the design doc as-is in a comment inside the body of the "it.todo" test.

Examples

WIP class example

/**
 * @deprecated 🚧 work in progress
 */
class Greetings {
  hello() {
    throw new Error(`🚧 work in progress`);
  }
}

WIP method example

class Greetings {
  /**
   * @deprecated 🚧 work in progress
   */
  hello() {
    throw new Error(`🚧 work in progress`);
  }
}

WIP component

/**
 * @deprecated 🚧 work in progress
 */
@Component({
  changeDetection: ChangeDetectionStrategy.OnPush,
  selector: "wm-rules",
  template: `Rules - 🚧 work in progress`,
})
class Rules {
  rules = input.required<Rule[]>();
  ruleSelect = output<Rule>();
}

WIP tests example

Note: test names start in lower case (e.g. "search rules ...").

import { describe, it } from "vitest";

describe(RuleSearch.name, () => {
  it.todo("search rules without filtering", () => {
    // mount RuleSearch
    // click on first rule
    // assert output was triggered once
  });

  it.todo("...", () => {
    // ...
  });
});

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Continues Charted Coding work for a PR by routing to scaffold, red, or green based on design doc progress. Use when resuming work on a PR, continuing TDD after a break, or when the user invokes charted continue with a design doc and PR number.

The English summary is being prepared. Showing the original description.

testmex/testmex4Updated Jul 23, 2026

Interviews the user section by section to collaboratively produce design documents. Use when creating a design doc, starting feature design, or when the user invokes the design command.

The English summary is being prepared. Showing the original description.

testmex/testmex4Updated Jul 23, 2026

Progressively activates todo tests one at a time, updates implementation code until each passes (verified via Wallaby), checks off matching design doc progress, then moves to the next—following the design doc as the single source of truth.

The English summary is being prepared. Showing the original description.

testmex/testmex4Updated Jul 23, 2026

Runs Charted Coding iterations in a loop — route via charted-continue, batch red or green work for an entire test file, commit, then repeat until the PR is complete. Infers design doc and PR number when omitted. Use when the user invokes charted loop, wants batch TDD for a PR test file, or asks to continue charted work with commits.

The English summary is being prepared. Showing the original description.

testmex/testmex4Updated Jul 23, 2026

Writes the next failing test based on provided design doc and existing todo tests

The English summary is being prepared. Showing the original description.

testmex/testmex4Updated Jul 23, 2026

Reviews a design doc with expert sub-agents

The English summary is being prepared. Showing the original description.

testmex/testmex4Updated Jul 23, 2026

See all skills by testmex

Report a problem with this skill